Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Directly assigned as a result of owning RHEL9 bug.
I did not reset target release to 8.5 as I'm not sure that will be possible. It's an engineering decision in the long run, but would involve trying to apply more recent upstream changes to an older qemu since RHEL 8.5 was based on qemu-4.2, while RHEL 8.6 and beyond will be based on qemu-6.2.
Cloning this bug to resolve a RHEL-AV bug is technically possible, but not preferred.
David Gilbert created an issue for implementing this at Libvirt gitlab repo:
https://gitlab.com/libvirt/libvirt/-/issues/306
I am not sure if someone is already working on that, but I could see no merge request nor master commit related to that.
So, I am currently trying to understand how to add that in libvirt, but honestly I am very new to the code, and I am still not sure how it should be done.
Hi leonardo,
Thanks for the update of DTM and ITM. Just a reminder here that DTM 18 is July 4, can we get the available qemu-kvm downstream before that?
Since QE also needs at least one week to test this future feature. I would suggest move ITR from 8.7.0 to 8.8.0 if we still can't make the qemu-kvm available in downstream before DTM 18/19.
Thanks for the understand!
Verify this bug on qemu-kvm-6.2.0-18.module+el8.7.0+15999+d24f860e.x86_64, same test results as https://bugzilla.redhat.com/show_bug.cgi?id=1968509#c23
I have cloned one bug for RHEL 8.7.0:
Bug 2110203 - zerocopy capability can be enabled when set migrate capabilities with multifd and compress/xbzrle together
For dst qemu crash issue under postcopy + multifd scenario, I will wait for Leonardo's reply to decide to whether need to clone:
https://bugzilla.redhat.com/show_bug.cgi?id=2106726#c1
Mark this bug as verified per above test results.
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 (Low: virt:rhel and virt-devel:rhel 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-2022:7472