Bug 2170930

Description of problem:

The /usr/libexec/xen/boot/ovmf.bin firmware provided by the xen-runtime package lacks Xen support. See this report for more details:

https://bugzilla.redhat.com/show_bug.cgi?id=2170730

Version-Release number of selected component (if applicable):

All Fedora releases of xen-runtime since at least Fedora 36.

How reproducible:

Always.

Steps to Reproduce:

1. Install the xen component if not already installed.
2. Reboot Fedora 36 or 37 (or rawhide, probably) as dom0 on the Xen hypervisor package provided by the Fedora xen component if not already running Fedora as Xen dom0.
3. Download a Fedora Live iso file and configure a guest to boot it in a Xen HVM using the bios = 'ovmf' option in the xen libxl domain configuration file. I tested using the vga = 'stdvga' Qemu video driver and the vnc display options in the libxl domain configuration file and connected to the guest using a vnc viewer.

Actual results:

The guest hangs indefinitely, with a message stating the guest has not initialized the display yet. Neither the Tiano Core boot screen is displayed nor the grub boot menu is displayed, and the only way to stop the guest is to destroy it with the 'xl destroy' command (or 'virsh destroy' if using libvirt as frontend to libxl).

Expected results:

The Tiano core screen and then the grub menu should display and allow the user to boot the Fedora Live disk and test Fedora live out and optionally install Fedora to a virtual hard disk in a Xen HVM that uses the ovmf firmware.

Additional info:

A recent update to Fedora helps fix this issue:

https://bodhi.fedoraproject.org/updates/FEDORA-2023-951bd0eeaf

With the update, users can install the new edk2-ovmf-xen package and configure the guest to use the correct firmware with xen support by adding the following options to the xl domain configuration file:

bios = 'ovmf'
bios_path_override = '/usr/share/edk2/xen/OVMF.fd'

I am requesting that future releases of the xen-runtime package depend on the new edk2-ovmf-xen package (at least as a Recommended depend) and that future releases of xen will be configured to use the /usr/share/edk2/xen/OVMF.fd firmware by default when the guest is configured with bios = 'ovmf' instead of using the current firmware that xen-runtime provides (/usr/libexec/xen/boot/ovmf.bin) because that firmware lacks support for Xen and is essentially useless.

It will not be necessary for the xen source package to have a build dependency on edk2-ovmf anymore with this proposed change.

Other related links to help explain why this fix is needed:

https://bugzilla.tianocore.org/show_bug.cgi?id=2122
https://bbs.archlinux.org/viewtopic.php?id=269628

Thanks.