UEFI guests not loading console
-
@Mefosheez Looks like a OVMF bug to me (issue with PML5e ?).
What CPU are you using ?
-
@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.
-
@Mefosheez So it is not concerned with (potential) PML5e issues.
Have you tried rebooting the host ?
-
@Mefosheez I would try it on that other host you have and see if you run into the same issues, just for good measure.
Are they managed by the same XO? Maybe you can just migrate it to the other host so it's the exact same VM.
-
@TeddyAstie I did a reboot but not change.
@planedrop They are and I will do it this afternoon.
Thanks.
-
@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!
-
@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)
-
@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.
-
The only experience that I have is Server 2025 Eval with an older Xeon, vtpm, vsecure boot, vuefi and no problems with default configuration using win2022 template and turning on the above mentioned settings.
The only real difference is that I always uncheck automatic boot during creation, go into advanced and change the Intel NIC, save and then initial boot.
I mention that all of the settings are virtual because my old servers do not support hardware uefi or hardware tpm 2.0 so all of that must be synthetic for my lab.
I'm also using up to date XCP 8.3 with this VM.
-
M Mefosheez referenced this topic on
-
@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
-
M Mefosheez referenced this topic on
-
M Mefosheez marked this topic as a question on
