From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:41067) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vdgm1-0007DX-8L for qemu-devel@nongnu.org; Tue, 05 Nov 2013 08:34:33 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Vdgls-0000iH-QU for qemu-devel@nongnu.org; Tue, 05 Nov 2013 08:34:25 -0500 Received: from mail-wi0-x236.google.com ([2a00:1450:400c:c05::236]:54339) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vdgls-0000iA-Jn for qemu-devel@nongnu.org; Tue, 05 Nov 2013 08:34:16 -0500 Received: by mail-wi0-f182.google.com with SMTP id ez12so2059738wid.15 for ; Tue, 05 Nov 2013 05:34:15 -0800 (PST) Date: Tue, 5 Nov 2013 14:34:12 +0100 From: Stefan Hajnoczi Message-ID: <20131105133412.GD16457@stefanha-thinkpad.redhat.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] [migration] questions about removing the old block-migration code List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Zhanghaoyu (A)" Cc: "Huangweidong (C)" , "Michael S. Tsirkin" , Michal Privoznik , Linqiangmin , Marcelo Tosatti , "paolo.bonzini@gmail.com" , "qemu-devel@nongnu.org" , Xiahai , "quintela@redhat.com" , Zanghongyong , Luonengjun , "Huangpeng (Peter)" On Sun, Nov 03, 2013 at 04:01:36AM +0000, Zhanghaoyu (A) wrote: > I read below words on the report of , > We were going to remove the old block-migration code > Then people fixed it > Good: it works now > Bad: We have to maintain both > It uses the same port than migration > You need to migrate all/none of block devices > > The old block-migration code said above is that in block-migration.c? Yes. > What are the reasons of removing the old block-migration code? Buggy implementation? Or need to migrate all/none of block devices? Buggy and tightly coupled with the live migration code, making it hard to modify either area independently. > What's the substitutional method? drive_mirror? drive_mirror over NBD is an alternative. There are security and integration challenges with those approaches but libvirt has added drive-mirror block migration support. Stefan