RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1654276 - qemu-kvm: Should depend on the architecture-appropriate guest firmware
Summary: qemu-kvm: Should depend on the architecture-appropriate guest firmware
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: qemu-kvm
Version: 8.0
Hardware: All
OS: Linux
medium
low
Target Milestone: rc
: 8.0
Assignee: Danilo de Paula
QA Contact: Chao Yang
URL:
Whiteboard:
Depends On:
Blocks: 1660208
TreeView+ depends on / blocked
 
Reported: 2018-11-28 11:38 UTC by Andrea Bolognani
Modified: 2019-06-14 01:36 UTC (History)
10 users (show)

Fixed In Version: qemu-kvm-2.12.0-52.module+el8+2617+8f1b8f17
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1660208 (view as bug list)
Environment:
Last Closed: 2019-06-14 01:36:00 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Andrea Bolognani 2018-11-28 11:38:04 UTC 
The spec file for qemu-kvm currently contains

  %ifarch %{ix86} x86_64
  Requires: seabios-bin >= 1.10.2-1
  Requires: sgabios-bin
  %endif
  %ifnarch aarch64 s390x
  Requires: seavgabios-bin >= 1.10.2-1
  Requires: ipxe-roms-qemu >= 20170123-1
  %endif
  %ifarch %{power64}
  Requires: SLOF >= %{SLOF_gittagdate}-1.git%{SLOF_gittagcommit}
  %endif

This ensures SeaBIOS and SLOF are always installed along with QEMU
on the respective architectures, which is good; however, the same is
not true of OVMF (a fully-supported alternative to SeaBIOS for x86_64
guests) or AAVMF (the only firmware available for aarch64 guests). I
have no idea how guest firmware works on s390x, so I won't comment on
that.

We should introduce additional Requires: lines so that users wont't
have to worry about guest firmware at all, regardless of the
architecture they're using, and the user experience will be entirely
consistent.
Comment 3 Danilo de Paula 2018-12-14 17:09:30 UTC 
Can you please clarify what's the firmware for each archtecture?

% ifarch x86_64
BuildRequires: edk2-ovmf
%endif

% ifarch aarch64
BuildRequires: edk2-aaarch64
%endif
Comment 4 Laszlo Ersek 2018-12-14 20:05:49 UTC 
Hi Danilo,

that's right -- because we only support hardware virtualization, host and guest architecture should match. Therefore, on aarch64 hosts, edk2-aarch64 should be a dependency, and on x86_64 hosts, edk2-ovmf should be.

Please note that these should be runtime dependencies (i.e., "Requires", not "BuildRequires").

Thanks!
Comment 5 Danilo de Paula 2018-12-17 19:34:53 UTC 
QA_ACK please
Comment 9 Danilo de Paula 2018-12-19 12:42:38 UTC 
Fix is ready waiting for QA_ACK+ to be built.
Comment 13 Danilo de Paula 2019-01-04 12:41:18 UTC 
Fix included in qemu-kvm-2.12.0-52.module+el8+2617+8f1b8f17
Comment 15 Chao Yang 2019-01-22 03:22:07 UTC 
For aarch64:

# rpm -qp --requires qemu-kvm-core-2.12.0-57.module+el8+2683+02b3b955.aarch64.rpm 
/bin/sh
edk2-aarch64


For x86_64:

# rpm -qp --requires qemu-kvm-core-2.12.0-57.module+el8+2683+02b3b955.x86_64.rpm 
/bin/sh
edk2-ovmf

# rpm -ivh /home/qemu-kvm-core-2.12.0-57.module+el8+2683+02b3b955.x86_64.rpm 
error: Failed dependencies:
	edk2-ovmf is needed by qemu-kvm-core-15:2.12.0-57.module+el8+2683+02b3b955.x86_64

Currently, QE doesn't test aarch64 so setting VERIFIED
Comment 16 Chao Yang 2019-01-22 03:27:31 UTC 
(In reply to Chao Yang from comment #15)
> For aarch64:
> 
> # rpm -qp --requires
> qemu-kvm-core-2.12.0-57.module+el8+2683+02b3b955.aarch64.rpm 
> /bin/sh
> edk2-aarch64
> 
> 
> For x86_64:
> 
> # rpm -qp --requires
> qemu-kvm-core-2.12.0-57.module+el8+2683+02b3b955.x86_64.rpm 
> /bin/sh
> edk2-ovmf
> 
> # rpm -ivh /home/qemu-kvm-core-2.12.0-57.module+el8+2683+02b3b955.x86_64.rpm 
> error: Failed dependencies:
> 	edk2-ovmf is needed by
> qemu-kvm-core-15:2.12.0-57.module+el8+2683+02b3b955.x86_64
> 

dnf module install virt:rhel worked fine which has qemu-kvm-core-15:2.12.0-57.module+el8+2683+02b3b955.x86_64 and edk2-ovmf-20180508gitee3198e672e2-8.el8.noarch installed correctly.

> Currently, QE doesn't test aarch64 so setting VERIFIED
Note You need to log in before you can comment on or make changes to this bug.