Bug 2143585

Summary:	Update machine type compatibility for QEMU 7.2.0 update [s390x]
Product:	Red Hat Enterprise Linux 9	Reporter:	Miroslav Rezanina <mrezanin>
Component:	qemu-kvm	Assignee:	Thomas Huth <thuth>
qemu-kvm sub component:	Machine Types	QA Contact:	smitterl
Status:	CLOSED ERRATA	Docs Contact:
Severity:	medium
Priority:	medium	CC:	bfu, clegoate, coli, jinzhao, juzhang, smitterl, thuth, virt-maint
Version:	9.2	Keywords:	Triaged
Target Milestone:	rc
Target Release:	9.2
Hardware:	s390x
OS:	Linux
Whiteboard:
Fixed In Version:	qemu-kvm-7.2.0-1.el9	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-05-09 07:20:51 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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