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 2111784 - Update machine type compatibility for QEMU 7.1.0 update [s390x]
Summary: Update machine type compatibility for QEMU 7.1.0 update [s390x]
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: qemu-kvm
Version: 9.2
Hardware: s390x
OS: Linux
medium
medium
Target Milestone: rc
: 9.2
Assignee: Thomas Huth
QA Contact: smitterl
URL:
Whiteboard:
Depends On:
Blocks: 2111769
TreeView+ depends on / blocked
 
Reported: 2022-07-28 08:04 UTC by Miroslav Rezanina
Modified: 2022-09-12 21:48 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-09-12 21:48:31 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-129376 0 None None None 2022-07-28 08:27:49 UTC

Description Miroslav Rezanina 2022-07-28 08:04:46 UTC
With rebase to QEMU 7.1.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.

Comment 2 Thomas Huth 2022-08-15 10:23:03 UTC
As far as I can see, we don't need any changes this time, apart from the "hw_compat_rhel_9_1" modification that you already did with your "Introduce upstream 7.0 compat changes" patch, Mirek.
( @dhildenb could you maybe double-check? )

I'll keep looking at the upcoming release candidates of QEMU 7.1, but if nothing else is added with regards to machine type compatibility, I think we can close this BZ as soon as QEMU 7.1 has been released.

Comment 3 David Hildenbrand 2022-08-23 06:46:17 UTC
(In reply to Thomas Huth from comment #2)
> As far as I can see, we don't need any changes this time, apart from the
> "hw_compat_rhel_9_1" modification that you already did with your "Introduce
> upstream 7.0 compat changes" patch, Mirek.
> ( @dhildenb could you maybe double-check? )

I can primarily only spot changes to the QEMU CPU model.

For rhel9.0.0, it should remain unchanged as we explicitly set it to a z14 already, and the upstream change to a z15 shouldn't become active here.

I assume we're good.

Comment 4 Thomas Huth 2022-08-24 10:42:01 UTC
Thanks for double-checking, David! So unless something pops up in the final week before upstream QEMU 7.1 gets released, I think we can finally close this next week.

Comment 5 Thomas Huth 2022-09-12 21:48:31 UTC
AFAIK there were no changes in the final 7.1 release anymore, so we can close this now.


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