Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionMiroslav Rezanina
2022-11-17 10:05:35 UTC
With rebase to QEMU 7.2.0 we have to update compatibility bits for qemu-kvm package so we keep old machine types stable.
Please add necessary changes to ensure all machine types are compatible with previous versions.
Mirek - in your opinion, is this different than bug 2131982? If so, then please be sure this bug gets added to the machine type epic; otherwise, close as duplicate.
Comment 3Miroslav Rezanina
2022-11-21 05:52:52 UTC
Yes, this is different. We can introduce new machine type after rebase is done but compatibility has to be solved before rebase.
There is nothing that needs to be updated as of now (-rc2 time), and I don't see anything on the list that would need to be included.
Moving to POST; I expect we can simply close this when 7.2 is out.
Pre-verify with qemu-kvm-7.2.0-2.el9
# /usr/libexec/qemu-kvm -M ?
Supported machines are:
virt RHEL 9.2.0 ARM Virtual Machine (alias of virt-rhel9.2.0)
virt-rhel9.2.0 RHEL 9.2.0 ARM Virtual Machine (default)
virt-rhel9.0.0 RHEL 9.0.0 ARM Virtual Machine
none empty machine
Test Environment:
Host Distro: RHEL-9.2.0-20221220.0 BaseOS aarch64
Host Kernel: kernel-5.14.0-217.el9.aarch64
QEMU: qemu-kvm-7.2.0-2.el9.aarch64
edk2: edk2-aarch64-20220826gitba0e0e4c6a-2.el9.noarch
Guest: RHEL.9.2.0
Results Analysis:
From 83 tests executed, 82 passed and 0 warned - success rate of 98.80% (excluding SKIP and CANCEL)
The failed case is due to an existing all platform bug
New bugs(0):
Existing bugs(0):
Job link:
http://10.0.136.47/7363114/results.html
Will also update the test result of virt-9.0.0 machine type later, because it also includes a change: compat_props_add(mc->compat_props, hw_compat_rhel_9_1, hw_compat_rhel_9_1_len);
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Moderate: qemu-kvm security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2023:2162