Bug 1668956 - incremental backup bitmap API needs a finalized interface
Summary: incremental backup bitmap API needs a finalized interface
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm-rhev
Version: 7.7
Hardware: All
OS: All
Target Milestone: rc
: ---
Assignee: John Snow
QA Contact: aihua liang
Depends On:
Blocks: 1691009
TreeView+ depends on / blocked
Reported: 2019-01-24 00:27 UTC by John Snow
Modified: 2019-08-22 09:20 UTC (History)
5 users (show)

Fixed In Version: qemu-kvm-rhev-2.12.0-27.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1691009 (view as bug list)
Last Closed: 2019-08-22 09:19:59 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2019:2553 None None None 2019-08-22 09:20:49 UTC

Description John Snow 2019-01-24 00:27:19 UTC
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.

Comment 1 Miroslav Rezanina 2019-04-25 03:52:00 UTC
Fix included in qemu-kvm-rhev-2.12.0-27.el7

Comment 4 aihua liang 2019-05-15 04:54:26 UTC
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

Comment 6 errata-xmlrpc 2019-08-22 09:19:59 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, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.