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:08:42 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 2137327? 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:53:00 UTC
Yes, this is different. We can introduce new machine type after rebase is done but compatibility has to be solved before rebase.
Comment 4Dr. David Alan Gilbert
2022-11-21 11:42:09 UTC
The code I posed in 2137327 already has the compat and the new machine type all in one.