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.
The following commits occur in mdroth's stable-2.0-staging branch, which I have tested to be enough for upstream libvirt to drive active commit with the upcoming qemu 2.0.1, when coupled with the existing active commit support in qemu 2.0. Since downstream qemu-kvm-rhev-1.5.3-60.el7_0_0.5.x86_64 has already picked everything related to active commit from qemu 2.0, it is probably just these remaining patches required before downstream libvirt can drive active commit.
3c548f6 mirror: Fix qiov size for short requests
d0d83e8 qemu-iotests: Test 0-length image for mirror
98103fa block: make 'top' argument to block-commit optional
e5f0eb0 qemu-iotests: Test BLOCK_JOB_READY event for 0Kb image active commit
43ac708 mirror: Go through ready -> complete process for 0 len image
8e09e20 blockjob: Add block_job_yield()
520b341 mirror: Fix resource leak when bdrv_getlength fails
Here's what they were picked from:
$ git log -7 mdroth/stable-2.0-staging | grep cherry
(cherry picked from commit 5a0f6fd5c84573387056e0464a7fc0c6fb70b2dc)
(cherry picked from commit 3b9f27d2b34cb8c5cc6cec993712c7e1943e9de9)
(cherry picked from commit 7676e2c597000eff3a7233b40cca768b358f9bc9)
(cherry picked from commit 8b9a30ca5bc10545637429486836f3c206c39fab)
(cherry picked from commit 9e48b025400b2d284e17860862b0a4aa02c6032d)
(cherry picked from commit dc71ce45ded4e872e25c2de32d5e7a71842b0985)
(cherry picked from commit 373df5b135b4a54e0abb394e9e703fef3ded093c)
Comment 4Miroslav Rezanina
2014-08-21 08:26:07 UTC
Reassigned to qemu-kvm component as main target for this fix is 7.0.z. Although qemu-kvm-rhev package is affected, 7.0.z uses shared code for qemu-kvm and qemu-kmv-rhev and we track all issues for these packages in qemu-kvm component.
As i understand, the patch set is to advertise active commit to libvirt, not functional one for qemu itself, so to kvm qe, only need to insure current function is not affected, coded related includes live commit, block mirror and iotests test suite, so three runs at least is recommended to verify this bug.
Comment 7Miroslav Rezanina
2014-08-26 14:04:01 UTC
The following commits occur in mdroth's stable-2.0-staging branch, which I have tested to be enough for upstream libvirt to drive active commit with the upcoming qemu 2.0.1, when coupled with the existing active commit support in qemu 2.0. Since downstream qemu-kvm-rhev-1.5.3-60.el7_0_0.5.x86_64 has already picked everything related to active commit from qemu 2.0, it is probably just these remaining patches required before downstream libvirt can drive active commit. 3c548f6 mirror: Fix qiov size for short requests d0d83e8 qemu-iotests: Test 0-length image for mirror 98103fa block: make 'top' argument to block-commit optional e5f0eb0 qemu-iotests: Test BLOCK_JOB_READY event for 0Kb image active commit 43ac708 mirror: Go through ready -> complete process for 0 len image 8e09e20 blockjob: Add block_job_yield() 520b341 mirror: Fix resource leak when bdrv_getlength fails Here's what they were picked from: $ git log -7 mdroth/stable-2.0-staging | grep cherry (cherry picked from commit 5a0f6fd5c84573387056e0464a7fc0c6fb70b2dc) (cherry picked from commit 3b9f27d2b34cb8c5cc6cec993712c7e1943e9de9) (cherry picked from commit 7676e2c597000eff3a7233b40cca768b358f9bc9) (cherry picked from commit 8b9a30ca5bc10545637429486836f3c206c39fab) (cherry picked from commit 9e48b025400b2d284e17860862b0a4aa02c6032d) (cherry picked from commit dc71ce45ded4e872e25c2de32d5e7a71842b0985) (cherry picked from commit 373df5b135b4a54e0abb394e9e703fef3ded093c)