From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:39861) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YkZTv-0002v1-H0 for qemu-devel@nongnu.org; Tue, 21 Apr 2015 10:49:00 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YkZTu-0000oN-Pa for qemu-devel@nongnu.org; Tue, 21 Apr 2015 10:48:59 -0400 Date: Tue, 21 Apr 2015 16:48:50 +0200 From: Kashyap Chamarthy Message-ID: <20150421144850.GH5761@tesla.redhat.com> References: <1427484005-31120-1-git-send-email-jsnow@redhat.com> <5531ACD6.9030208@redhat.com> <20150421135311.GB11726@tesla.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150421135311.GB11726@tesla.redhat.com> Subject: Re: [Qemu-devel] [PATCH v2.5 00/10] block: incremental backup transactions List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: John Snow Cc: kwolf@redhat.com, famz@redhat.com, qemu-block@nongnu.org, qemu-devel@nongnu.org, mreitz@redhat.com, vsementsov@parallels.com, stefanha@redhat.com 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