-
-
Notifications
You must be signed in to change notification settings - Fork 48
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
UEFI enabled HVMs hang on "Guest has not initialized the display (yet)" #8625
Comments
What I think is happening (And I might be wrong). So as for temporary solution, it is possible to get ovmf.bin firmware from R4.1 installation that still has Xen support (located at /usr/libexec/xen/boot/ovmf.bin) and place it in /usr/libexec/xen/boot/ovmf.bin in new R4.2 installation. With that, HVMs with uefi boot enabled work. references: |
Thank you, for mentioning the workaround. I had the same problem, fetched the R4.1 Update: My HVM/UEFI qube never had a PCI device attached and it still got stuck with |
It works for HVM without PCI devices attached to it. |
Yeah, this solution will only enable you to boot HVMs with uefi boot enabled. But soon as you add PCI devices to that HVM, it will get stuck again. I'll try to see whats wrong today or tomorrow. |
This looks like a Xen build system bug. There is no way that Xen should be building an |
I don't think Xen builds OVMF at all. It looks to be taken from edk2-ovmf Fedora's package. I guess that's the problem, looking at Fedora package, it should be |
This fixes two bugs: 1. The bundled OVMF didn't support Xen, so UEFI guests failed to boot. 2. The bundled OVMF didn't include the license text alongside it. Fixes: QubesOS/qubes-issues#8625
Qubes OS release
Fresh install of 4.2-RC4
Brief summary
After upgrading to 4.2, UEFI enabled HVMs won't boot anymore and will just hang on
Guest has not initialized the display (yet)
Steps to reproduce
qvm-features <vm-name> uefi 1
Expected behavior
HVM with UEFI boot enabled boots.
Actual behavior
It hangs while displaying the message
Guest has not initialized the display (yet)
The text was updated successfully, but these errors were encountered: