<![CDATA[Client hangs at EFI stub:]]>I am trying to get fog to deploy a CentOS image that I have to a server. The firmware was updated on the server and now deploy is not working. It keeps hanging at EFI stub: Measured initrd data into PCR 9
I have tried several things to try and get past this error but nothing is working. Here is my setup.
Fog version: 1.5.10
fos version: 31.03.2023 Kernel 6.1.22
ipxe version: (g0aa2e)

d51ac539-c6fb-475f-814a-658f7a50631f-image.png

I believe this has to do with security but am not sure how to get past it.
Thanks for any help that I can get.
Steve

]]>http://forums.fogproject.org/topic/16993/client-hangs-at-efi-stubRSS for NodeThu, 11 Jun 2026 06:38:36 GMTTue, 05 Sep 2023 22:46:35 GMT60<![CDATA[Reply to Client hangs at EFI stub: on Tue, 30 Jul 2024 22:25:27 GMT]]>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

]]>http://forums.fogproject.org/post/155277http://forums.fogproject.org/post/155277Tue, 30 Jul 2024 22:25:27 GMT<![CDATA[Reply to Client hangs at EFI stub: on Fri, 29 Dec 2023 17:43:48 GMT]]>@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.

]]>http://forums.fogproject.org/post/153961http://forums.fogproject.org/post/153961Fri, 29 Dec 2023 17:43:48 GMT<![CDATA[Reply to Client hangs at EFI stub: on Tue, 19 Dec 2023 16:58:54 GMT]]>@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.

]]>http://forums.fogproject.org/post/153936http://forums.fogproject.org/post/153936Tue, 19 Dec 2023 16:58:54 GMT<![CDATA[Reply to Client hangs at EFI stub: on Tue, 19 Dec 2023 15:31:32 GMT]]>@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

]]>http://forums.fogproject.org/post/153935http://forums.fogproject.org/post/153935Tue, 19 Dec 2023 15:31:32 GMT<![CDATA[Reply to Client hangs at EFI stub: on Thu, 14 Dec 2023 17:43:06 GMT]]>@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?

]]>http://forums.fogproject.org/post/153903http://forums.fogproject.org/post/153903Thu, 14 Dec 2023 17:43:06 GMT<![CDATA[Reply to Client hangs at EFI stub: on Thu, 14 Dec 2023 00:34:34 GMT]]>@sgilbe Okay, I did some changes and reuploaded dist_virt_1 & dist_virt_2. Can you try them again?

]]>http://forums.fogproject.org/post/153886http://forums.fogproject.org/post/153886Thu, 14 Dec 2023 00:34:34 GMT<![CDATA[Reply to Client hangs at EFI stub: on Wed, 13 Dec 2023 22:26:47 GMT]]>@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.

]]>http://forums.fogproject.org/post/153885http://forums.fogproject.org/post/153885Wed, 13 Dec 2023 22:26:47 GMT<![CDATA[Reply to Client hangs at EFI stub: on Mon, 11 Dec 2023 17:20:47 GMT]]>@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

]]>http://forums.fogproject.org/post/153860http://forums.fogproject.org/post/153860Mon, 11 Dec 2023 17:20:47 GMT<![CDATA[Reply to Client hangs at EFI stub: on Thu, 07 Dec 2023 18:59:14 GMT]]>@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.

]]>http://forums.fogproject.org/post/153826http://forums.fogproject.org/post/153826Thu, 07 Dec 2023 18:59:14 GMT<![CDATA[Reply to Client hangs at EFI stub: on Tue, 05 Dec 2023 19:08:41 GMT]]>@rodluz I have tried all 3 kernels the dist1 has the same issue. dist2 and 3 show the following message.

25ab355c-7b60-48ac-a7dd-b9aaa0fe9f16-image.png

Then they go back to the main menu.

]]>http://forums.fogproject.org/post/153806http://forums.fogproject.org/post/153806Tue, 05 Dec 2023 19:08:41 GMT<![CDATA[Reply to Client hangs at EFI stub: on Tue, 05 Dec 2023 19:03:30 GMT]]>@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.

]]>http://forums.fogproject.org/post/153805http://forums.fogproject.org/post/153805Tue, 05 Dec 2023 19:03:30 GMT<![CDATA[Reply to Client hangs at EFI stub: on Tue, 05 Dec 2023 17:20:49 GMT]]>@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.

]]>http://forums.fogproject.org/post/153803http://forums.fogproject.org/post/153803Tue, 05 Dec 2023 17:20:49 GMT<![CDATA[Reply to Client hangs at EFI stub: on Tue, 05 Dec 2023 16:48:03 GMT]]>@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.

]]>http://forums.fogproject.org/post/153802http://forums.fogproject.org/post/153802Tue, 05 Dec 2023 16:48:03 GMT<![CDATA[Reply to Client hangs at EFI stub: on Tue, 05 Dec 2023 16:25:53 GMT]]>@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.

]]>http://forums.fogproject.org/post/153801http://forums.fogproject.org/post/153801Tue, 05 Dec 2023 16:25:53 GMT<![CDATA[Reply to Client hangs at EFI stub: on Tue, 05 Dec 2023 11:09:03 GMT]]>@rodluz @sgilbe Hi, I just found a workarround.

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

]]>http://forums.fogproject.org/post/153796http://forums.fogproject.org/post/153796Tue, 05 Dec 2023 11:09:03 GMT<![CDATA[Reply to Client hangs at EFI stub: on Mon, 04 Dec 2023 20:41:06 GMT]]>@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?

]]>http://forums.fogproject.org/post/153793http://forums.fogproject.org/post/153793Mon, 04 Dec 2023 20:41:06 GMT<![CDATA[Reply to Client hangs at EFI stub: on Mon, 04 Dec 2023 17:54:02 GMT]]>@sgilbe Hi, sorry for the delay.
I have 3 new kernels to try. I hope one of these works for you https://drive.google.com/drive/folders/1sP6dfRymYaFTCr8iRiK64hN2pp2X836n?usp=drive_link

If any one of these works, please let me know which one so I can document it.

]]>http://forums.fogproject.org/post/153791http://forums.fogproject.org/post/153791Mon, 04 Dec 2023 17:54:02 GMT<![CDATA[Reply to Client hangs at EFI stub: on Mon, 04 Dec 2023 16:51:35 GMT]]>@SaturTP I am glad I am not the only one having this issue. Hopefully we can figure out what is causing the issue and get a fix implemented. Currently we are imaging our systems with this issue by hand which is taking a lot more time. I have it on a Quanta and a SMC server as well.

]]>http://forums.fogproject.org/post/153790http://forums.fogproject.org/post/153790Mon, 04 Dec 2023 16:51:35 GMT<![CDATA[Reply to Client hangs at EFI stub: on Mon, 04 Dec 2023 16:20:40 GMT]]>I have the same problem on a HP Z8 G5 dual Xeon silver 4410Y some kernels show just the first line, others bothIMG_20231204_171625.jpg

]]>http://forums.fogproject.org/post/153789http://forums.fogproject.org/post/153789Mon, 04 Dec 2023 16:20:40 GMT<![CDATA[Reply to Client hangs at EFI stub: on Thu, 30 Nov 2023 16:34:12 GMT]]>@george1421 Yes secure boot is disabled. Here is a picture of the BIOS setting.

5dc8880c-28df-493c-87c6-1d8aed0d112b-image.png

]]>http://forums.fogproject.org/post/153771http://forums.fogproject.org/post/153771Thu, 30 Nov 2023 16:34:12 GMT<![CDATA[Reply to Client hangs at EFI stub: on Wed, 29 Nov 2023 22:58:33 GMT]]>@sgilbe I’m not seeing anything that jumps out at me as being wrong. It surely seems to fail at starting the kernel.

Are you sure you don’t have secure boot enabled on this system?

]]>http://forums.fogproject.org/post/153768http://forums.fogproject.org/post/153768Wed, 29 Nov 2023 22:58:33 GMT<![CDATA[Reply to Client hangs at EFI stub: on Wed, 29 Nov 2023 22:35:41 GMT]]>@george1421 I have been able to get a debug BIOS for my system and was able to capture from a serial port more detail. I know it has been a while since this was updated but was thinking this could give more light to the issue. This is not the full file it is just from the select boot device (USB Drive) to the hang.

Debug out:
Disabling CR4.SMXE…
-> Register 0x11: Pause Resume Complete = 0x01 0x01 0x00
CheckpointSend 0x08? Yes
-> Register 0x11: Pause Resume Complete = 0x01 0x01 0x01
CheckpointSend 0x09? Yes
-> Ready To Boot: Pause Resume Complete = 0x01 0x01 0x01
[HECI Transport-1 DXE] Send pkt: 80040007
00: FF 0C 00 00
[HECI Transport-1 DXE] Got pkt: 80080007
00: FF 8C 00 00 00 00 00 00
IioSecureOnOnReadyToBoot…
IOAT_INIT_READY_TO_BOOT_START
IOAT_INIT_READY_TO_BOOT_END
IOAT_INIT_READY_TO_BOOT_START
IOAT_INIT_READY_TO_BOOT_END
[TDX_LATE] TdxDxeCallbackOnReadyToBoot BEGIN
[TDX_LATE-GET_FROM_ESP] GetTdxSeamldrFromEsp BEGIN
[LoadFileFromEsp] BEGIN
[TDX_LATE-GET_FROM_ESP] Open (Not Found)
[TDX_LATE-GET_FROM_ESP] Open (Not Found)
[TDX_LATE-GET_FROM_ESP] Error (Not Found)
[TDX_LATE-GET_FROM_ESP] GetTdxSeamldrFromEsp END (Not Found)
Error: Unable find TdxSeamldr in ESP
[TDX_LATE-GET_FROM_FV] GetTdxSeamldrFromFv BEGIN
[TDX_LATE-GET_FROM_FV] GetTdxSeamldrFromFv END (Success)
TdxSeamldrAddress (FV): 0x63392018
TdxSeamldrSize (FV): 0x35000
[TDX_LATE-GET_FROM_ESP] GetTdxSeamFromEsp BEGIN
[LoadFileFromEsp] BEGIN
[TDX_LATE-GET_FROM_ESP] Open (Not Found)
[TDX_LATE-GET_FROM_ESP] Open (Not Found)
[TDX_LATE-GET_FROM_ESP] Error (Not Found)
[TDX_LATE-GET_FROM_ESP] GetTdxSeamFromEsp END (Not Found)
Error: Unable find TdxSeam in ESP, aborting!
Unable to find TDX binaries in ESP, falling back to FV!
[TDX_LATE-GET_FROM_FV] GetTdxSeamFromFv BEGIN
[TDX_LATE-GET_FROM_FV] GetTdxSeamFromFv END (Success)
TdxSeamAddress (FV): 0x63344018
TdxSeamSize (FV): 0x26000
[TDX_LATE-GET_FROM_FV] GetTdxSeamSigFromFv BEGIN
[TDX_LATE-GET_FROM_FV] GetTdxSeamSigFromFv END (Success)
TdxSeamSigAddress (FV): 0x64E12018
TdxSeamSigSize (FV): 0x800
[TDX_LATE-HANDLE_SEAMLDR] HandleTdxSeamldr BEGIN
[TDX_LATE-HANDLE_SEAMLDR] ValidateSeamldrBinary BEGIN
[TDX_LATE-HANDLE_SEAMLDR] ValidateSeamldrBinary END (Success)
[TDX_LATE-HANDLE_SEAMLDR] ProgramTdxSeamldrSeSvn BEGIN
Extracted SE_SVN = 0x04 from ACM_HEADER!
Extracted SE_SVN = 0x00 from NVRAM!
Seamldr SE_SVN = 0x04 selected from ACM_HEADER!
[TDX_LATE-HANDLE_SEAMLDR] ProgramTdxSeamldrSeSvn END (Success)
[TDX_LATE-HANDLE_SEAMLDR] LoadTdxSeamldr BEGIN
AsmLaunchTdxSeamldr BEGIN (0x6330F000)
AsmLaunchTdxSeamldr END (0x0)
[TDX_LATE-HANDLE_SEAMLDR] LoadTdxSeamldr END (Success)
[TDX_LATE-HANDLE_SEAMLDR] HandleTdxSeamldr END (Success)
[TDX_LATE-HANDLE_SEAM] HandleTdxSeam BEGIN
[TDX_LATE-VMX] BaseFruUcode4v0_SetCrsForVmx BEGIN
[TDX_LATE-VMX] BaseFruUcode4v0_SetCrsForVmx END (Success)
[TDX_LATE-VMX] VmxOnAndSeamcallThenVmxOffOnAllLps BEGIN
[TDX_LATE-VMX] VmxOnAndSeamcallThenVmxOffOnAllLps END (Success)
[TDX_LATE-HANDLE_SEAM] HandleTdxSeam END (Success)
[TDX_LATE] TdxDxeCallbackOnReadyToBoot END
SmmInstallProtocolInterface: 6E057ECF-FA99-4F39-95BC-59F9921D17E4 0
[SmbiosIFWI] Get Ifwi Version failed.
[HECI Transport-1 DXE] Send pkt: 80040007
00: FF 02 00 00
[HECI Transport-1 DXE] Got pkt: 80140007
00: FF 82 00 00 01 00 06 18 - 30 00 02 00 01 00 06 18
10: 30 00 02 00
TPM Location configured (expected values: dTPM = 0x5 = 0x5
Value at TPM Base Address (0xFED40000) = 0xA1
HierarchyChangeAuth: Response Code error! 0x000009A2
PROGRESS CODE: V03051001 I0
PROGRESS CODE: V03058000 I0
PROGRESS CODE: V03058001 I0
GNU GRUB version 2.06

/----------------------------------------------------------------------------\||||||||||||||||||||||||||----------------------------------------------------------------------------/ Use the ^ and v keys to select which entry is highlighted.

  Press enter to boot the selected OS, `e' to edit the commands       

  before booting or `c' for a command-line.                            *1. FOG Image Deploy/Capture                                                 2. Perform Full Host Registration and Inventory                             3. Quick Registration and Inventory                                         4. Client System Information (Compatibility)                                5. Run Memtest86+                                                           6. FOG Debug Kernel                                                         7. FOG iPXE Jumpstart BIOS                                                  8. FOG iPXE Jumpstart EFI                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              1. FOG Image Deploy/Capture                                                *2. Perform Full Host Registration and Inventory                             2. Perform Full Host Registration and Inventory                            *3. Quick Registration and Inventory                                         3. Quick Registration and Inventory                                        *4. Client System Information (Compatibility)                                4. Client System Information (Compatibility)                               *5. Run Memtest86+                                                           5. Run Memtest86+                                                          *6. FOG Debug Kernel                                                        loading the kernel

loading the virtual hard drive

booting kernel…

IioSecureOnExitBootServices…
SmmInstallProtocolInterface: 296EB418-C4C8-4E05-AB59-39E8AF56F00A 0
EnablePatrolScrubatEndofPostCallback Exit
PROGRESS CODE: V03101019 I0

]]>http://forums.fogproject.org/post/153767http://forums.fogproject.org/post/153767Wed, 29 Nov 2023 22:35:41 GMT<![CDATA[Reply to Client hangs at EFI stub: on Wed, 08 Nov 2023 00:21:49 GMT]]>@rodluz Is it possible to try and get a new kernel with version 6.6.0 I have been told it could fix this issue.

]]>http://forums.fogproject.org/post/153621http://forums.fogproject.org/post/153621Wed, 08 Nov 2023 00:21:49 GMT<![CDATA[Reply to Client hangs at EFI stub: on Wed, 18 Oct 2023 18:06:05 GMT]]>@sgilbe After removing the card it is still hanging.

]]>http://forums.fogproject.org/post/153486http://forums.fogproject.org/post/153486Wed, 18 Oct 2023 18:06:05 GMT