Imported VM Starts but Does Not Initialize the Display
-
@kagbasi-ngc I was inviting you to have a look first, but I'll try to give it a look. Still, try to find something relevant in them, it's a good troubleshooting exercise.
-
Relevant logs, from
daemon.log
:Dec 12 05:08:18 VMH01 qemu-dm-1[8691]: SyncPcrAllocationsAndPcrMask! Dec 12 05:08:18 VMH01 qemu-dm-1[8691]: Set PcdTpm2Hash Mask to 0x0000000F Dec 12 05:08:19 VMH01 qemu-dm-1[8691]: AllocatePages failed: No 0x8400 Pages is available. Dec 12 05:08:19 VMH01 qemu-dm-1[8691]: There is only left 0x3AA8 pages memory resource to be allocated. Dec 12 05:08:19 VMH01 qemu-dm-1[8691]: ERROR: Out of aligned pages Dec 12 05:08:19 VMH01 qemu-dm-1[8691]: ASSERT /builddir/build/BUILD/edk2-20220801/MdeModulePkg/Core/DxeIplPeim/X64/VirtualMemory.c(814): BigPageAddress != 0
ERROR: Out of aligned pages
does not look good to me. -
@stormi My apologies. Normally I relish the opportunity to dive deep into logs, however, in this case I am also the treasurer of my church and I have year-end accounting tasks to accomplish, so haven't had much time to dedicate to this.
Additionally, since I don't really know what I'm looking for in the logs, I figured it's be best to share it on hear for the community to take a look...lol.
-
@stormi Yikes! If you're spooked by this error, then what does this mean for me?
By the way, this very VM imported and started up without any issues on a physical XCP-ng host. This issue seems to be happening in a nested virtualization setting - where XCP-ng is the nested hypervisor (a guest of VMware Workstation Pro).
-
@kagbasi-ngc Don't do nesting! It's not to be trusted even when it seems to work.
-
@manilx Yeah, not doing it in production, just in a test environment. Plus I only did it because I actually found a write-up by the Vates team on how to get it done, which confirmed to me that while they don't recommend it for production, they understand that it has some merit in a testing environment and want to see it working.
That said, I definitely hear your admonition and would never do it in a production setting.
-
I'm not spooked, I just think it's the relevant error message we need to understand :).
Since this is a test pool, could you make it use the debug version of OVMF?
ln -sf OVMF-debug.fd /usr/share/edk2/OVMF.fd
Then attempt to start the VM again, and get
/var/log/daemon.log
and/var/log/xensource.log
once again. -
@stormi Glad you're not spooked....
I'll enable the debug mode as you'd instructed and grab the logs for you shortly.
-
@stormi Hi there, as requested, here are the two logs:
I started the VM at timestamp Dec 13 13:54:59 and stopped it at Dec 13 13:55:59.
Now, is deleting the symbolic link created above all that is necessary to reverse the debug mode?
-
@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.
-
-
@kagbasi-ngc Looks like we missed something, as the log indicates it loaded
OVMF-release.fd
:Dec 13 13:54:59 VMH01 xenguest-2-build[8345]: Loaded OVMF from /usr/share/edk2/OVMF-release.fd
We'll come back to you with a better test procedure.
For now I just have a quick and dirty one, consisting in overwriting the release file with the debug one:
cp /usr/share/edk2/OVMF-debug.fd /usr/share/edk2/OVMF-release.fd
You can revert this change with
yum reinstall edk2
. -
@stormi Sorry for the delayed reply. I did as you requested, and below are the resulting log files. I started the VM at timestamp Dec 17 14:43:34 and stopped it about 2 minutes later.
If I can be of assistance, don't hesitate to ask please. Thank you.