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 2143585 - Update machine type compatibility for QEMU 7.2.0 update [s390x]
Summary: Update machine type compatibility for QEMU 7.2.0 update [s390x]
Keywords:
Status: CLOSED ERRATA
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:
TreeView+ depends on / blocked
 
Reported: 2022-11-17 10:08 UTC by Miroslav Rezanina
Modified: 2023-05-09 07:47 UTC (History)
8 users (show)

Fixed In Version: qemu-kvm-7.2.0-1.el9
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-09 07:20:51 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gitlab redhat/rhel/src/qemu-kvm qemu-kvm merge_requests 232 0 None None None 2022-11-18 16:22:47 UTC
Red Hat Bugzilla 2136473 0 medium CLOSED Add rhel-9.2.0 s390x machine type 2023-05-12 03:54:37 UTC
Red Hat Issue Tracker RHELPLAN-139780 0 None None None 2022-11-17 10:12:09 UTC
Red Hat Product Errata RHSA-2023:2162 0 None None None 2023-05-09 07:21:21 UTC

Internal Links: 2136473

Description Miroslav Rezanina 2022-11-17 10:08:39 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.
Comment 2 John Ferlan 2022-11-17 12:07:39 UTC 
Mirek - in your opinion, is this different than bug 2136473? If so, then please be sure this bug gets added to the machine type epic; otherwise, close as duplicate.
Comment 3 Thomas Huth 2022-11-18 16:25:17 UTC 
(In reply to John Ferlan from comment #2)
> Mirek - in your opinion, is this different than bug 2136473? If so, then
> please be sure this bug gets added to the machine type epic; otherwise,
> close as duplicate.

One BZ is for making sure that the old machine types get the right compatibility handling, and one BZ is for adding a new RHEL 9.2.0 machine type... I guess we could use one BZ for both ... or keep two BZs if we want to emphasis the distinction... I don't mind much - Anyway, I've posted now one MR that handles both issues.
Comment 4 Miroslav Rezanina 2022-11-21 05:53:58 UTC 
(In reply to Thomas Huth from comment #3)
> (In reply to John Ferlan from comment #2)
> > Mirek - in your opinion, is this different than bug 2136473? If so, then
> > please be sure this bug gets added to the machine type epic; otherwise,
> > close as duplicate.
> 
> One BZ is for making sure that the old machine types get the right
> compatibility handling, and one BZ is for adding a new RHEL 9.2.0 machine
> type... I guess we could use one BZ for both ... or keep two BZs if we want
> to emphasis the distinction... I don't mind much - Anyway, I've posted now
> one MR that handles both issues.


Yes, this is different. We can introduce new machine type after rebase is done but compatibility has to be solved before rebase.
Comment 5 smitterl 2022-12-19 14:54:05 UTC 
bi directional migration PASSED for:

machine type:
s390-ccw-virtio-rhel9.0.0

source:
qemu-kvm-7.0.0-13.el9.s390x

destination:
qemu-kvm-7.2.0-1.el9.s390x
Comment 9 bfu 2022-12-26 15:16:45 UTC 
Stable guest abi PASSED for:

machine type:
s390-ccw-virtio-rhel9.0.0

source:
qemu-kvm-7.0.0-13.el9.s390x

destination:
qemu-kvm-7.2.0-2.el9.s390x




Test log:http://10.0.136.47/bfu/s390x/bz2143585/

set this bz to verified
Comment 11 errata-xmlrpc 2023-05-09 07:20:51 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.