Client hangs at EFI stub:

[Tom Elliott]

@sgilbe Just a thought here, but is there a possible firmware update needed for these devices too?

I don’t think updating the kernels is going to be a bad thing but also ensuring the firmware is updated to the latest for efi stub integration seems the next potentially most logical step?

[SaturTP]

@rodluz @sgilbe Hi, I just found a workarround.

Disabling Virtualization, VTx and VTd makes it boot with every kernel at least in my case.

[sgilbe]

@Tom-Elliott I have updated all systems to the latest firmware versions. I will go and check to make sure again that I am on the latest versions of firmware.

[sgilbe]

@SaturTP I will try disabling virtualization however we do need that to be enabled on our servers. But if this works then at least it is pointing to the possible root of the issue.

[rodluz]

@SaturTP That’s an interesting find, I’ll check why this would be the problem.
@sgilbe If disabling virtualization makes it work for you too, I’ll add one more kernel to the drive share for you to try.

[sgilbe]

@SaturTP I have disabled Virtualization and VTd but unable to find VTx. So far with these two items it is still failing. Where did you find VTx. Just a generalized location will work hopefully.

[sgilbe]

@rodluz I have tried all 3 kernels the dist1 has the same issue. dist2 and 3 show the following message.

Then they go back to the main menu.

[sgilbe]

@rodluz Are you able to try enabling virtualization in the kernel to see if it fixes it for SaturTP maybe it will help me my issue as well.

[rodluz]

@sgilbe I uploaded two more kernels with virtualization enabled (dist_virt_1 & dist_virt_2). Let me know if this works for you.
https://drive.google.com/drive/folders/1sP6dfRymYaFTCr8iRiK64hN2pp2X836n

[sgilbe]

@rodluz These both give me the same error after loading the kernel. Error: kernel doesn’t support EFI handover. This is the same error I was getting with dist 2 and 3. dist 1 did not give this error.

[rodluz]

@sgilbe Okay, I did some changes and reuploaded dist_virt_1 & dist_virt_2. Can you try them again?

[sgilbe]

@rodluz thank you for your current help on this. I have tried both the 2 new images you have provided and they are both failing back at the booting kernel that I see when I try to boot the original kernels off the USB drive. Would it be helpful for you to be able to remotely access the system and login to it?

[jfernandz]

@SaturTP said in Client hangs at EFI stub::

@rodluz @sgilbe Hi, I just found a workarround.

Disabling Virtualization, VTx and VTd makes it boot with every kernel at least in my case.

I can confirm just disabling VT the kernel boots , thank you @SaturTP

[sgilbe]

@rodluz I got it working. I was able to boot into the debug kernel from the usb and was able to get it to boot into the deploy image.

I disabled Virtualization, VT-d, and X2APIC

I was missing the X2APIC setting once that was disabled it started working. thank you all for your help in getting this working.

[sgilbe]

@rodluz After disabling VT and X2APIC Intel x2APIC Mode disabling these settings and the system properly deploying an image what setting in the kernel would need to change to allow for the system to deploy properly without having to modify the BIOS settings? I think this may be easier said then done but want to start looking at it.

[sgilbe]

Using the latest experimental fos kernel I am able to deploy via task without issues. https://github.com/FOGProject/fos/releases/tag/EXP_20240720

Thank you all for your help in getting this to work.

This can be marked as Solved