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 2135806 - Rebase to QEMU 7.2 for RHEL 9.2.0
Summary: Rebase to QEMU 7.2 for RHEL 9.2.0
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: qemu-kvm
Version: 9.2
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Miroslav Rezanina
QA Contact: jingzhao
URL:
Whiteboard:
Depends On:
Blocks: 1924193 1963845 1983208 1983493 1986665 2072155 2074000 2091166 2120480 2122788 2124446 2126095 2129761 2136797 2137330 2137332 2144436 2152977 2161784
TreeView+ depends on / blocked
 
Reported: 2022-10-18 13:27 UTC by John Ferlan
Modified: 2023-07-28 23:41 UTC (History)
11 users (show)

Fixed In Version: qemu-kvm-7.2.0-1.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-09 07:20:41 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-136897 0 None None None 2022-10-18 13:33:14 UTC
Red Hat Product Errata RHSA-2023:2162 0 None None None 2023-05-09 07:22:20 UTC

Description John Ferlan 2022-10-18 13:27:05 UTC
Description of problem:

Let's rebase qemu-kvm to the most recent upstream version.

Will set ITR=9.2.0 and DTM=15 as a target knowing that upstream qemu releases sometime in late November or early November per their plan:

https://wiki.qemu.org/Planning/7.2

This needs to be completed before 15-Jan in order to be ready for Comprehensive Test Cycle 2.

Comment 1 John Ferlan 2022-12-09 16:52:15 UTC
Can we get qa_ack to keep the release+ bot happy and not delay Mirek?

I also adjusted DTM+1 to avoid the bot and acknowledging that the upstream release is not out yet.

Comment 2 Miroslav Rezanina 2022-12-15 08:14:22 UTC
Rebase build failing (on CentOS only) due to linker issue - https://issues.redhat.com/browse/CS-1313

Comment 3 Miroslav Rezanina 2022-12-16 12:40:09 UTC
Builders fixed but Zuul CI still failing - https://issues.redhat.com/browse/ZUUL-33

Comment 4 Yanan Fu 2022-12-20 08:39:17 UTC
QE bot(pre verify): Set 'Verified:Tested,SanityOnly' as gating/tier1 test pass.

Comment 10 errata-xmlrpc 2023-05-09 07:20:41 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.