From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=51782 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PuFja-0006u1-VH for qemu-devel@nongnu.org; Mon, 28 Feb 2011 21:54:48 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PuFjW-0001mN-RT for qemu-devel@nongnu.org; Mon, 28 Feb 2011 21:54:46 -0500 Received: from mx1.redhat.com ([209.132.183.28]:47166) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PuFjW-0001mH-Hb for qemu-devel@nongnu.org; Mon, 28 Feb 2011 21:54:42 -0500 Date: Mon, 28 Feb 2011 23:35:54 -0300 From: Marcelo Tosatti Subject: Re: [Qemu-devel] [patch 2/3] Add support for live block copy Message-ID: <20110301023554.GA27777@amt.cnet> References: <20110222170004.808373778@redhat.com> <20110222170115.710717278@redhat.com> <4D655AC6.3090503@codemonkey.ws> <20110226000214.GA30160@amt.cnet> <4D690408.1020404@codemonkey.ws> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4D690408.1020404@codemonkey.ws> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Jes.Sorensen@redhat.com, qemu-devel@nongnu.org, avi@redhat.com On Sat, Feb 26, 2011 at 07:45:44AM -0600, Anthony Liguori wrote: > >>>+- "filename": target image filename (json-string) > >>Is this a created image? Is this an image to create? > >A previously created image. > > > >>To future proof for blockdev, we should make this argument optional > >>and if it's not specified throw an error about missing argument. > >>This let's us introduce an optional blockdev argument such that we > >>can use a blockdev name. > >What you mean "blockdev"? > > -drive file=image.qcow2,if=none,id=foo > > 'foo' is a named blockdev. We don't have a way to add these through > the monitor (yet) but we will for 0.15. Fail to see the point of having a named blockdev to specify the target? > >>If I resume the > >>operation with the incremental flag set, will it Just Work? > >As in: > > > >- block_copy ide0-hd1 /mnt/aa.img > >- block_copy ide0-hd1 /mnt/aa.img -i > > > >? > > > >The second command will fail with QERR_BLOCKCOPY_IN_PROGRESS. > > No, as in: > > block_copy ide0-hd1 /mnt/aa.img > block_copy_cancel ide0-h1 > block_copy ide0-h1 /mnt/aa.img -i > > Does it pick up where it left off or does it start all over again? It starts all over again.