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.

Description of problem:

The pull-model incremental backup API still uses commands like "x-block-dirty-bitmap-disable" and several others. The API should be finalized for use by Libvirt/RHV and others.

Version-Release number of selected component (if applicable):

Seen in 7.7's qemu-kvm-rhev-2.12.0; fixed upstream in QEMU 3.1 development branches.

Fix included in qemu-kvm-rhev-2.12.0-27.el7

Have verified on qemu-kvm-rhev-2.12.0-27.el7.x86_64, the bug has been fixed, will set bug's status to "Verified".

The left issue will be tracked by the following new bugs:
      Bug 1703916 - Qemu core dump when quit vm after forbidden to do backup with a read-only bitmap
      Bug 1707303 - Error returned qmp info when do incremental live backup with an in-use bitmap
      Bug 1707733 - Qemu hang when do backup jobs with completion-mode "grouped" and with one job failed
      Bug 1707821 - Target VM failed to enter running status after migration with persistent bitmap on shared storage

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, 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-2019:2553