On Tue, Apr 21, 2015 at 03:53:11PM +0200, Kashyap Chamarthy wrote: [. . .]
> And, invoking `drive-backup` *without* pre-creating the target image > (i.e. 'incremental.o.img'): > > { 'execute': 'drive-backup', > 'arguments': { > 'device': 'ide0-0-0', Small typo (in this email, not in my test): s/ide0-0-0/drive-ide0-0-0 > 'bitmap': 'bitmap0', > 'sync': 'dirty-bitmap', > 'target': 'incremental.0.img', > 'mode': 'existing', > 'format': 'qcow2' > } > } > > Results in: > > {"QMP": {"version": {"qemu": {"micro": 93, "minor": 2, "major": 2}, > "package": ""}, "capabilities": []}} {"return": {}} > > Instead of an "error". Is this a bug? > > On a related note, Kevin Wolf said on IRC that he gets an error > (without 'bitmap') when tested from QEMU master branch. On a separate machine, I tested the above behavior with master (f2a5810), but I don't see any error, without 'bitmap' and with 'mode' as 'existing', i.e.: { 'execute': 'drive-backup', 'arguments': { 'device': 'drive-virtio-disk0', 'sync': 'full', 'target': '/var/lib/libvirt/images/incremental.0.img', 'mode': 'existing', 'format': 'qcow2' } } still results in: {"return": {}} Maybe I doing something wrong? -- /kashyap