On Mon, Jun 10, 2019 at 21:49:51 -0500, Eric Blake wrote:
> On 6/7/19 2:08 AM, Peter Krempa wrote:
> > On Thu, Jun 06, 2019 at 08:41:26 -0500, Eric Blake wrote:
> >> On 6/6/19 7:48 AM, Peter Krempa wrote:
> >>> On Wed, Jun 05, 2019 at 22:01:09 -0500, Eric Blake wrote:
> The upcoming
On 6/7/19 2:08 AM, Peter Krempa wrote:
> On Thu, Jun 06, 2019 at 08:41:26 -0500, Eric Blake wrote:
>> On 6/6/19 7:48 AM, Peter Krempa wrote:
>>> On Wed, Jun 05, 2019 at 22:01:09 -0500, Eric Blake wrote:
The upcoming virDomainBackup() API needs to take advantage of various
qcow2 bitmap
On Thu, Jun 06, 2019 at 08:41:26 -0500, Eric Blake wrote:
> On 6/6/19 7:48 AM, Peter Krempa wrote:
> > On Wed, Jun 05, 2019 at 22:01:09 -0500, Eric Blake wrote:
> >> The upcoming virDomainBackup() API needs to take advantage of various
> >> qcow2 bitmap manipulations as the basis to
On 6/6/19 7:48 AM, Peter Krempa wrote:
> On Wed, Jun 05, 2019 at 22:01:09 -0500, Eric Blake wrote:
>> The upcoming virDomainBackup() API needs to take advantage of various
>> qcow2 bitmap manipulations as the basis to virDomainCheckpoints and
>> incremental backups. Add four functions to expose
On Wed, Jun 05, 2019 at 22:01:09 -0500, Eric Blake wrote:
> The upcoming virDomainBackup() API needs to take advantage of various
> qcow2 bitmap manipulations as the basis to virDomainCheckpoints and
> incremental backups. Add four functions to expose
>
The upcoming virDomainBackup() API needs to take advantage of various
qcow2 bitmap manipulations as the basis to virDomainCheckpoints and
incremental backups. Add four functions to expose
block-dirty-bitmap-{add,enable,disable,merge} (this is the
recently-added QEMU_CAPS_BITMAP_MERGE capability).
