Bug 2170930 - Please configure xen to use new edk2-ovmf-xen package
Summary: Please configure xen to use new edk2-ovmf-xen package
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: xen
Version: rawhide
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Michael Young
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-02-17 17:59 UTC by Chuck Zmudzinski
Modified: 2023-03-06 00:53 UTC (History)
3 users (show)

Fixed In Version: xen-4.16.3-3.fc37 xen-4.16.3-3.fc36
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-02-22 10:11:48 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Chuck Zmudzinski 2023-02-17 17:59:40 UTC
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.

Comment 1 Fedora Update System 2023-02-18 12:20:06 UTC
FEDORA-2023-dad0295b25 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2023-dad0295b25

Comment 2 Chuck Zmudzinski 2023-02-18 15:48:05 UTC
(In reply to Fedora Update System from comment #1)
> FEDORA-2023-dad0295b25 has been submitted as an update to Fedora 36.
> https://bodhi.fedoraproject.org/updates/FEDORA-2023-dad0295b25

I can try and test this update in a snapshot on top of my Fedora 37 installation but would prefer to wait until an update is submitted to Fedora 37.

Do you plan to submit this fix as an update to Fedora 37?

Thanks.

Comment 3 Fedora Update System 2023-02-19 01:48:20 UTC
FEDORA-2023-dad0295b25 has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-dad0295b25`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-dad0295b25

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 4 Fedora Update System 2023-02-19 08:10:21 UTC
FEDORA-2023-ce97a665a1 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-ce97a665a1

Comment 5 Fedora Update System 2023-02-20 03:01:53 UTC
FEDORA-2023-ce97a665a1 has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-ce97a665a1`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-ce97a665a1

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2023-02-22 10:11:48 UTC
FEDORA-2023-ce97a665a1 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 7 Fedora Update System 2023-03-06 00:53:47 UTC
FEDORA-2023-dad0295b25 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.