-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
XCP-NG 8.3 kernel loading issue in EFI mode with iPXE + multiboot2 patches #663
Comments
Just a thought: could you try to use iPXE with debug mode in case it provides more info? |
That task is already on my list, i will report back results once i tried that. |
I just rebuild iPXE with DEBUG=segment, the resulting error is:
|
After some more testing, it seems that this is only happening on my test VM which is running on an XCP-NG 8.2 Host. The problem is still a bit weird because the older installer (8.2.1) boots just fine also in a VM. |
That's weird indeed, but getting working on real hardware is the most important thing and a good news in the end. |
How do you get the VM to boot on your patched iPXE? |
Our dhcp server is presenting my iPXE by tftp to the VM/physical machines. It loads a menu structure which is dynamically created from single .boot files. One of it for XCP 8.3.0 has the following content:
|
Does the refreshed 8.2.1 installer also boot fine? |
I was already testing with the updated 8.2.1 installer. It worked fine. |
Adding @ydirson to the conversation. |
Hi same here in nested mode, with an ESXi 8.0 U3b running on a Xeon E5-2470 v2 CPU. I cannot boot the 8.3.0 installer, either in BIOS or UEFI mode. It starts booting, and the VM is restarted after a few seconds. |
@Fredouye Are you using iPXE to boot? |
Hi,
i just tried to invenst some time to get XCP-NG installer booted in EFI mode using iPXE + multiboot2 patches.
It's working fine for XCP-NG 8.2.1 but not for the new 8.3.0 release. It looks like the kernel behaves somewhat different. Maybe there were some changes in the build process?
The resulting error message from iPXE is:
The text was updated successfully, but these errors were encountered: