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 2027697 - Rebase to QEMU 6.2.0
Summary: Rebase to QEMU 6.2.0
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: qemu-kvm
Version: 9.0
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Miroslav Rezanina
QA Contact: jingzhao
URL:
Whiteboard:
Depends On:
Blocks: 1947015 2027636
TreeView+ depends on / blocked
 
Reported: 2021-11-30 13:08 UTC by Miroslav Rezanina
Modified: 2022-05-17 12:32 UTC (History)
13 users (show)

Fixed In Version: qemu-kvm-6.2.0-1.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-17 12:25:10 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 2022602 1 high CLOSED Update machine type compatibility for QEMU 6.2.0 update [s390x][RHEL-9.0.0] 2023-06-02 07:45:17 UTC
Red Hat Bugzilla 2032267 1 low CLOSED [wrb][qemu-kvm 6.2] qemu-kvm: vfio: Cannot reset device $vf_pci_address, depends on group 93 which is not owned. 2023-09-22 04:27:22 UTC
Red Hat Bugzilla 2035006 1 unspecified CLOSED interface availability is wrong on a restored machine 2022-01-18 15:06:26 UTC
Red Hat Issue Tracker RHELPLAN-104299 0 None None None 2021-11-30 13:09:35 UTC
Red Hat Product Errata RHBA-2022:2307 0 None None None 2022-05-17 12:25:57 UTC

Description Miroslav Rezanina 2021-11-30 13:08:54 UTC 
QEMU is large project and it is not trivial to do backporting for bigger changes. To keep backporting task reasonable complicated we need to do regular updates. 

QEMU 6.2.0 is final version we are targeting to get in RHEL 9.0.0.
Comment 1 Yanan Fu 2021-12-20 09:42:52 UTC 
QE bot(pre verify): Set 'Verified:Tested,SanityOnly' as gating/tier1 test pass.
Comment 4 smitterl 2021-12-23 11:48:48 UTC 
Yanan, Mirek, there are two integration issues with libvirt (one at least is critical), by setting ON_QA these issues will reproduce in the nightly. Could you please reconsider the pre-verification status. The two integration issues are:

https://bugzilla.redhat.com/show_bug.cgi?id=2022602#c5
https://bugzilla.redhat.com/show_bug.cgi?id=2035006

IIRC, the pre-verification was introduced to support Always-Ready-RHEL and help improve nightly compose quality, that is, no change should ever break the nightly.

I remember there's a team agreement that per default gating PASS is considered enough to consider a BZ pre-verified, but given that we have evidence of two integration issues - one most likely critical - I think we should hold bakc.
Comment 5 smitterl 2021-12-23 13:53:54 UTC 
(In reply to smitterl from comment #4)
> Yanan, Mirek, there are two integration issues with libvirt (one at least is
> critical), by setting ON_QA these issues will reproduce in the nightly.
> Could you please reconsider the pre-verification status. The two integration
> issues are:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=2022602#c5
... is Verified:Tested now using 6.0 <> 6.2 - https://bugzilla.redhat.com/show_bug.cgi?id=2022602#c8
> https://bugzilla.redhat.com/show_bug.cgi?id=2035006
... not sure about this one, Yalan, what do you think?
> IIRC, the pre-verification was introduced to support Always-Ready-RHEL and
> help improve nightly compose quality, that is, no change should ever break
> the nightly.
> 
> I remember there's a team agreement that per default gating PASS is
> considered enough to consider a BZ pre-verified, but given that we have
> evidence of two integration issues - one most likely critical - I think we
> should hold bakc.
Comment 6 yalzhang@redhat.com 2021-12-28 06:37:04 UTC 
(In reply to smitterl from comment #5)
> (In reply to smitterl from comment #4)
> > Yanan, Mirek, there are two integration issues with libvirt (one at least is
> > critical), by setting ON_QA these issues will reproduce in the nightly.
> > Could you please reconsider the pre-verification status. The two integration
> > issues are:
> > 
> > https://bugzilla.redhat.com/show_bug.cgi?id=2022602#c5
> ... is Verified:Tested now using 6.0 <> 6.2 -
> https://bugzilla.redhat.com/show_bug.cgi?id=2022602#c8
> > https://bugzilla.redhat.com/show_bug.cgi?id=2035006
> ... not sure about this one, Yalan, what do you think?
I hope this one can be fixed ASAP as it is a common scenario and it becomes kind of a test blocker for libvirt now.
Comment 9 Miroslav Rezanina 2022-01-12 15:08:57 UTC 
(In reply to smitterl from comment #4)
> Yanan, Mirek, there are two integration issues with libvirt (one at least is
> critical), by setting ON_QA these issues will reproduce in the nightly.
> Could you please reconsider the pre-verification status. The two integration
> issues are:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=2022602#c5
> https://bugzilla.redhat.com/show_bug.cgi?id=2035006
> 
> IIRC, the pre-verification was introduced to support Always-Ready-RHEL and
> help improve nightly compose quality, that is, no change should ever break
> the nightly.
> 
> I remember there's a team agreement that per default gating PASS is
> considered enough to consider a BZ pre-verified, but given that we have
> evidence of two integration issues - one most likely critical - I think we
> should hold bakc.


As we discuss, the first issue was caused by wrong compat handling in 6.1 and is not critical one.

Second one needs more work and it is something not blocking basic usage so can be solved on top of rebase.
Comment 11 errata-xmlrpc 2022-05-17 12:25:10 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 (new packages: qemu-kvm), 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/RHBA-2022:2307
Note You need to log in before you can comment on or make changes to this bug.