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.

qemu-kvm version:qemu-kvm-6.1.0-6.el9

reproduce rate: 10%

Assigning to Stefan to keep consistency with Bug #2021778, but let's keep the discussion and root-cause investigation there to avoid duplication.

(In reply to Klaus Heinrich Kiwi from comment #2)
> Assigning to Stefan to keep consistency with Bug #2021778, but let's keep
> the discussion and root-cause investigation there to avoid duplication.

assigning to the right Stefan, apologies for the noise.

Stefan posted patches upstream (https://bugzilla.redhat.com/show_bug.cgi?id=2021778#c6) perhaps a scratch build can be attempted to check if it addresses the fix?

The same patch that fixed the 8.6 bug (that this one was cloned from) is posted for 9.0 as fixing bug 2040123, and currently waiting to be included in the next build.

*** This bug has been marked as a duplicate of bug 2040123 ***