Offline
@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.
[08:30 xcp-r630 ~]# xl dmesg | grep HAP
(XEN) [ 2.581645] HVM: Hardware Assisted Paging (HAP) detected
(XEN) [ 2.584428] HVM: HAP page sizes: 4kB, 2MB, 1GB
This is not something I have ever adjusted or set prior.
@anthonyper said in Imported VM Starts but Does Not Initialize the Display:
yum update --enablerepo=xcp-ng-aperard1 edk2
confirmed with ubunutu desktop 24.02 in uefi. i can confirm windows later today but this looks to be the fix. will this be folded into an upcoming release?
@stormi thank you for the update. and @anthonyper for taking a look.
@stormi I marked it as a question about a week ago now. do you suggest making a new post as a question all together?
@stormi I wanted to follow up. I saw a good number of patches available today, first updates since the issues started for me. I processed them, but this issue still seems persist.
I know this thread is about nested virt, and i don't want to derail that. this is where i had posted about the issue prior. I believe they are going to be tided to the same root. any help would be appreciated.
https://xcp-ng.org/forum/topic/10083/uefi-guests-not-loading-console?_=1734014269146
@stormi thanks for the feedback. no rush here. just let me know if I can help.
@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)