From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:49282) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QTOhR-0005yB-Li for qemu-devel@nongnu.org; Sun, 05 Jun 2011 21:33:50 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QTOhQ-0000F2-SL for qemu-devel@nongnu.org; Sun, 05 Jun 2011 21:33:49 -0400 Received: from mx1.redhat.com ([209.132.183.28]:55985) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QTOhQ-0000Eu-I2 for qemu-devel@nongnu.org; Sun, 05 Jun 2011 21:33:48 -0400 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p561XkGu024734 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Sun, 5 Jun 2011 21:33:46 -0400 Date: Fri, 3 Jun 2011 13:20:27 -0300 From: Marcelo Tosatti Message-ID: <20110603162027.GA4956@amt.cnet> References: <20110523213115.164535428@amt.cnet> <20110523213411.003695437@amt.cnet> <4DE209C1.4080807@redhat.com> <20110531160636.GA9656@amt.cnet> <4DE51401.6040602@redhat.com> <20110531163858.GB9656@amt.cnet> <4DE51D18.9060309@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4DE51D18.9060309@redhat.com> Subject: Re: [Qemu-devel] [patch 6/7] QEMU live block copy List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: kwolf@redhat.com, Jes.Sorensen@redhat.com, dlaor@redhat.com, qemu-devel@nongnu.org On Tue, May 31, 2011 at 07:53:44PM +0300, Avi Kivity wrote: > >Don't see the need for that, management can simply wait for livecopy to > >finish or cancel livecopy and restart on destination after migration. > > They can do it, but I imagine it's pretty hard for them. Well, they have to handle migration failures anyway. > > >But yeah, it should be implemented sometime... > > > > > We should make an effort not to introduce interdependencies which > make management's life harder. While this is a good principle there is no way around complexity for management here. If migration is supported, the block copy target image filenames must be specified on the destination.