Skip to content
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

Open
netmax79 opened this issue Oct 8, 2024 · 12 comments
Open

Comments

@netmax79
Copy link

netmax79 commented Oct 8, 2024

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:

ipxe: Could not boot: Requested memory not available (https://ipxe.org/46038185)

@olivierlambert
Copy link
Member

Just a thought: could you try to use iPXE with debug mode in case it provides more info?

@netmax79
Copy link
Author

netmax79 commented Oct 8, 2024

That task is already on my list, i will report back results once i tried that.

@netmax79
Copy link
Author

netmax79 commented Oct 8, 2024

I just rebuild iPXE with DEBUG=segment, the resulting error is:

ipxe: Preparing segment [200000,836380,c00000)
ipxe: Segment [200000,836380,c00000) does not fit into available memory
ipxe: Could not boot: Requested memory not available (https://ipxe.org/46038185)

@netmax79
Copy link
Author

netmax79 commented Oct 8, 2024

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.
I tried to boot the same iPXE stack physical hardware (DELL R660) and that seems to work without any issue.

The problem is still a bit weird because the older installer (8.2.1) boots just fine also in a VM.

@olivierlambert
Copy link
Member

That's weird indeed, but getting working on real hardware is the most important thing and a good news in the end.

@stormi
Copy link
Member

stormi commented Oct 9, 2024

How do you get the VM to boot on your patched iPXE?

@netmax79
Copy link
Author

netmax79 commented Oct 10, 2024

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:

console
console --picture http://http.server/.ks/boot-xcpng.png --x 800 --y 600 --left 32 --right 32 --top 32 --bottom 48

set base-url http://http.server/xcp-ng/8.3.0

kernel ${base-url}/boot/xen.gz
module ${base-url}/boot/vmlinuz
module ${base-url}/install.img
imgargs xen.gz dom0_max_vcpus=1-16 dom0_mem=max:8192M com1=115200,8n1 console=com1,vga
imgargs vmlinuz xencons=hvc console=hvc0 console=tty0 device_mapper_multipath=enabled answerfile=http://http.server/.ks/xcp-ng83.cfg
boot

@stormi
Copy link
Member

stormi commented Oct 11, 2024

Does the refreshed 8.2.1 installer also boot fine?

@netmax79
Copy link
Author

I was already testing with the updated 8.2.1 installer. It worked fine.

@stormi
Copy link
Member

stormi commented Oct 29, 2024

Adding @ydirson to the conversation.

@Fredouye
Copy link

Fredouye commented Nov 27, 2024

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.
8.2.1 installer boots fine.

@stormi
Copy link
Member

stormi commented Nov 27, 2024

@Fredouye Are you using iPXE to boot?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants