From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:33207) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ykqzx-0004Vh-Dw for qemu-devel@nongnu.org; Wed, 22 Apr 2015 05:31:14 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Ykqzw-0003DR-CT for qemu-devel@nongnu.org; Wed, 22 Apr 2015 05:31:13 -0400 Date: Wed, 22 Apr 2015 11:31:01 +0200 From: Kevin Wolf Message-ID: <20150422093101.GD3882@noname.redhat.com> References: <1428055280-12015-1-git-send-email-wency@cn.fujitsu.com> <1428055280-12015-2-git-send-email-wency@cn.fujitsu.com> <20150420153047.GB32653@stefanha-thinkpad.redhat.com> <5535A727.5080402@cn.fujitsu.com> <55366C81.1080202@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <55366C81.1080202@redhat.com> Subject: Re: [Qemu-devel] [Qemu-block] [PATCH COLO v3 01/14] docs: block replication's description List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: Fam Zheng , Lai Jiangshan , qemu block , Stefan Hajnoczi , Jiang Yunhong , Dong Eddie , qemu devel , Max Reitz , Gonglei , Stefan Hajnoczi , Yang Hongyang , "Dr. David Alan Gilbert" , zhanghailiang Am 21.04.2015 um 17:28 hat Paolo Bonzini geschrieben: > > > On 21/04/2015 03:25, Wen Congyang wrote: > >> > Please do not introduce "+colo" block drivers. This approach is > >> > invasive and makes block replication specific to only a few block > >> > drivers, e.g. NBD or qcow2. > > NBD is used to connect to secondary qemu, so it must be used. But the primary > > qemu uses quorum, so the primary disk can be any format. > > The secondary disk is nbd target, and it can also be any format. The cache > > disk(active disk/hidden disk) is an empty disk, and it is created before run > > COLO. The cache disk format is qcow2 now. In theory, it can be ant format which > > supports backing file. But the driver should be updated to support colo mode. > > > > > A cleaner approach is a QMP command or -drive options that work for any > > > BlockDriverState. > > > > OK, I will add a new drive option to avoid use "+colo". > > Actually I liked the "foo+colo" names. > > These are just internal details of the implementations and the > primary/secondary disks actually can be any format. > > Stefan, what was your worry with the +colo block drivers? I haven't read the patches yet, so I may be misunderstanding, but wouldn't a separate filter driver be more appropriate than modifying qcow2 with logic that has nothing to do with the image format? Kevin