@Greg_E thanks for the feedback. I am stuck on this one. is either host or chipset specific and I don't have another e5-2680 v3 to test with. found another post on here around the same time frame that has this same error on boot. hope its not a broader issue.
https://xcp-ng.org/forum/topic/10075/imported-vm-starts-but-does-not-initialize-the-display
@stormi @kagbasi-ngc I have this same error in a separate thread, however, there is no nesting involved. from my limited knowledge, it seems like xcp is not seeing the available memory resources during boot and fails. if I migrate a running VM to the same host that gives me this error, it will operate as expected. but, after reboot... failure to launch.
https://xcp-ng.org/forum/topic/10083/uefi-guests-not-loading-console?_=1734014269146
@olivierlambert Thanks for your help so far.
@TeddyAstie Wanted to follow up and see if you had any insight on this pages error? I can confirm on a different host the VM will boot, I migrated it (live) back to the original host and it worked fine also, until I restarted it and then it failed the same way on boot up. same errors. thanks.
@Mefosheez said in UEFI guests not loading console:
@planedrop I found a sec to do this now. the host works as expected, the log is attached for boot. newhost-working.txt
So the the page allocation errors on the other host (lower level than I get normally) look to be uefi and qemu related. and the PML5e (found a white paper on it) seems to correlate as well. @TeddyAstie is there a reason you feel it is no longer relevant based on this chipset (e5-2680 v3)?
Thanks!
wanted to add that the initial migration failed with a "network required" error when moving from pool-wide eth3 to pool-wide eth0. I removed the existing vif (eth3), ran migrate, and then created a new vif (eth0)
@planedrop I found a sec to do this now. the host works as expected, the log is attached for boot. newhost-working.txt
So the the page allocation errors on the other host (lower level than I get normally) look to be uefi and qemu related. and the PML5e (found a white paper on it) seems to correlate as well. @TeddyAstie is there a reason you feel it is no longer relevant based on this chipset (e5-2680 v3)?
Thanks!
@TeddyAstie I did a reboot but not change.
@planedrop They are and I will do it this afternoon.
Thanks.
@TeddyAstie intel e5-2680
If it is useful for troubleshooting I have a different host in the pool with an i7-3770 I could try and deploy this on.
Thanks.
@planedrop notworking-uefi-new.txt working-bios-exisitng.txt
yes i bounced the other day for testing purposes. no different results.
attached is a tail on daemon.log
this, is it enforcing something it should not?
Dec 9 12:13:32 xcp-r630 varstored-17[1574285]: initialize_settings: Secure boot enable: false
Dec 9 12:13:32 xcp-r630 varstored-17[1574285]: initialize_settings: Authenticated variables: enforcing
and this, are the interesting bits. does it not see available memory?
Dec 9 12:13:33 xcp-r630 qemu-dm-17[1574330]: Detected Xen version 4.17
Dec 9 12:13:44 xcp-r630 qemu-dm-17[1574330]: AllocatePages failed: No 0x10400 Pages is available.
Dec 9 12:13:44 xcp-r630 qemu-dm-17[1574330]: There is only left 0x3929 pages memory resource to be allocated.
Dec 9 12:13:44 xcp-r630 qemu-dm-17[1574330]: ERROR: Out of aligned pages
Dec 9 12:13:44 xcp-r630 qemu-dm-17[1574330]: ASSERT /builddir/build/BUILD/edk2-20220801/MdeModulePkg/Core/DxeIplPeim/X64/VirtualMemory.c(814): BigPageAddress != 0
Thanks for the assist.
@planedrop confimred. I am running a similar (more resources) config on the ubuntu desktop VM.
I have not found any useful logs along the way with this. is there something more detailed in the in the cli?
@planedrop I have it on the Windows 11 VM, along with vTMP and other required settings. I have also tried enabling it on all the others as well while troubleshooting.
@planedrop Yeah I agree about it hanging, but I have it across multiple different OS and install types (below). no gpu passthrough to these specific VMs.
I had another install of home-assistant running for a few years and never had these issues with the console, and I believe that HAOS requires UEFI to boot. so, it was at a time working.
I have 9 or 10 other VMS running in this environment (all Bios) without issue. and only these three (UEFI) are affected. all three of these are on their initial install. so trying to get the ISO and VDI to load the install OS to manage in the console.
running Current version: 5.100.2, all hosts are patched.
I have three new VMs I can not finish installing because they require UEFI, and when this is enabled the console in XOA will not load the VM session. The console shows, "guest has not initialized display (yet)". it will hold on this indefinitely.
If I change these to Bios, I can get a console image but the OS will not boot. It seems like there is something I am overlooking, but I have been at this for a couple of days and have found nothing documenting this or others that have had the same issue.
any help would be appreciated.
@bullerwins said in Intel iGPU passthough:
@olivierlambert I tried but getting this error when turning on the VM
INTERNAL_ERROR(xenopsd internal error: (Failure
"Error from xenguesthelper: Populate on Demand and PCI Passthrough are mutually exclusive"))Not sure what it means
EDIT: after googleing it seems that static and dynamic memory has to be the same:
@bullerwins thanks for this. I had to restore a VM from a backup and while it was down changed the dynamic value. This certainly saved me some time. I was positive it had to do with remapping the UID on the VM or something on the host side of it. anyways, thanks.
