UEFI boot of guests doesn’t work at all

[DemiMarie]

How to file a helpful issue

Qubes OS release

R4.2

Brief summary

UEFI guests doesn’t work at all. The guest spins at 100% CPU without even initializing the QEMU-emulated display.

Steps to reproduce

Put an HVM guest in UEFI mode and start it:

$ qvm-prefs SOMEVM virt-mode hvm
$ qvm-prefs SOMEVM kernel ''
$ qvm-prefs SOMEVM debug True
$ qvm-features SOMEVM uefi 1
$ qvm-start SOMEVM

Expected behavior

SOMEVM starts, or at least displays something in the QEMU emulated display.

Actual behavior

SOMEVM hangs at 100% CPU without even initializing the emulated display.

This may be because there is no edk2-ovmf-xen package installed on the host.

[Nurmagoz]

Even though i have installed qubes on my pc with UEFI mode, templates are not using UEFI but instead on legacy boot. weird..

[apparatius]

Is it a duplicate of #8625?
Replacing /usr/libexec/xen/boot/ovmf.bin with the R4.1 one fetched from https://yum.qubes-os.org/r4.1/current/host/fc32/rpm/xen-runtime-4.14.6-4.fc32.x86_64.rpm works.

[DemiMarie]

Duplicate of #8625

[github-actions]

This issue has been closed as a "duplicate." This means that another issue exists that is very similar to or subsumes this one. If any useful information on this issue is not already present on the other issue, please add it in a comment on the other issue. Here are some common cases of duplicate issues:

• The other issue is closed. The other issue being closed does not prevent this issue from duplicating it. We will examine the closed issue and, if appropriate, reopen it.
• The other issue is for a different Qubes release. We usually maintain only one issue for all affected Qubes releases.
• The other issue is very old. The mere age of an issue is not, by itself, a relevant factor when determining duplicates.

By default, the newer issue will be closed in favor of the older issue. However, we make exceptions when we determine that it would be significantly more useful to keep the newer issue open instead of the older one.

We respect the time and effort you have taken to file this issue, and we understand that this outcome may be unsatisfying. Please accept our sincere apologies and know that we greatly value your participation and membership in the Qubes community.

If anyone reading this believes that this issue was closed in error or that the resolution of "duplicate" is not accurate, please leave a comment below saying so, and we will review this issue again. For more information, see How issues get closed.