On Fri, 12/19 09:20, Markus Armbruster wrote:
> Fam Zheng writes:
>
> > On Wed, 12/17 10:36, Markus Armbruster wrote:
> >> Fam Zheng writes:
> >>
> >> > Similar to drive-backup, but this command uses a device id as target
> >> > instead of creating/opening an image file.
> >> >
> >> > Also add
Fam Zheng writes:
> On Wed, 12/17 10:36, Markus Armbruster wrote:
>> Fam Zheng writes:
>>
>> > Similar to drive-backup, but this command uses a device id as target
>> > instead of creating/opening an image file.
>> >
>> > Also add blocker on target bs, since the target is also a named device
>>
On Wed, 12/17 10:36, Markus Armbruster wrote:
> Fam Zheng writes:
>
> > Similar to drive-backup, but this command uses a device id as target
> > instead of creating/opening an image file.
> >
> > Also add blocker on target bs, since the target is also a named device
> > now.
> >
> > Add check and
Fam Zheng writes:
> Similar to drive-backup, but this command uses a device id as target
> instead of creating/opening an image file.
>
> Also add blocker on target bs, since the target is also a named device
> now.
>
> Add check and report error for bs == target which became possible but is
> an
On Wed, Nov 05, 2014 at 10:57:09AM +0800, Fam Zheng wrote:
> +void qmp_blockdev_backup(const char *device, const char *target,
> + enum MirrorSyncMode sync,
> + bool has_speed, int64_t speed,
> + bool has_on_source_error,
> +
Similar to drive-backup, but this command uses a device id as target
instead of creating/opening an image file.
Also add blocker on target bs, since the target is also a named device
now.
Add check and report error for bs == target which became possible but is
an illegal case with introduction of
