From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:52293)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <dgilbert@redhat.com>) id 1ZD7wQ-0006yD-Rx
	for qemu-devel@nongnu.org; Thu, 09 Jul 2015 05:16:28 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <dgilbert@redhat.com>) id 1ZD7wP-00056p-T5
	for qemu-devel@nongnu.org; Thu, 09 Jul 2015 05:16:26 -0400
Date: Thu, 9 Jul 2015 10:16:11 +0100
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Message-ID: <20150709091610.GC2359@work-vm>
References: <559B1C92.90400@linux.vnet.ibm.com>
	<559B2669.8050509@cn.fujitsu.com> <20150707091323.GC2347@work-vm>
	<559B9A80.5080901@redhat.com> <559C04CE.4090103@linux.vnet.ibm.com>
	<559C7F06.3020100@cn.fujitsu.com>
	<559D4692.3060002@linux.vnet.ibm.com>
	<559DC78D.3060609@cn.fujitsu.com> <20150709015525.GF2741@work-vm>
	<559DD7CA.2050103@cn.fujitsu.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <559DD7CA.2050103@cn.fujitsu.com>
Subject: Re: [Qemu-devel] [PATCH COLO-BLOCK v7 00/17] Block replication for
 continuous checkpoints
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Wen Congyang <wency@cn.fujitsu.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Fam Zheng <famz@redhat.com>, Wen Congyang <ghostwcy@gmail.com>, qemu block <qemu-block@nongnu.org>, Jiang Yunhong <yunhong.jiang@intel.com>, Dong Eddie <eddie.dong@intel.com>, qemu devel <qemu-devel@nongnu.org>, "Michael R. Hines" <mrhines@linux.vnet.ibm.com>, Max Reitz <mreitz@redhat.com>, "Michael R. Hines" <mrhines@us.ibm.com>, Stefan Hajnoczi <stefanha@redhat.com>, Paolo Bonzini <pbonzini@redhat.com>, Yang Hongyang <yanghy@cn.fujitsu.com>, Lai Jiangshan <laijs@cn.fujitsu.com>

* Wen Congyang (wency@cn.fujitsu.com) wrote:

> >> I have sent the v8. But the usage is not changed. You can setup the environment according to the wiki.
> >> When we open nbd client, we need to connect to the nbd server. So I introduce a new command child_add to add NBD client
> >> as a quorum child when the nbd server is ready.
> >>
> >> The nbd server is ready after you run the following command:
> >> nbd_server_start 0:6262 # the secondary qemu will listen to host:port
> >> nbd_server_add -w mc1   # the NBD server will know this disk is used as NBD server. The export name is its id wc1.
> >>                         # -w means we allow to write to this disk.
> >>
> >> Then you can run the following command in the primary qemu:
> >> child_add disk1 child.driver=replication,child.mode=primary,child.file.host=127.0.0.1,child.file.port=6262,child.file.export=mc1,child.file.driver=nbd,child.ignore-errors=on
> >>
> >> After this monitor command, nbd client has connected to the nbd server.
> > 
> > Ah! The 'child.file.export=mc1' wasn't there previously; I see Yang added that to the wiki yesterday;
> > that probably explains the problem that we've been having.
> 
> Sorry for this mistake.

OK, so this is working for me (with the 7.2 world).   What isn't working in this setup is migrate -b, I get:

(qemu) Receiving block device images
Error unknown block device disk1
qemu-system-x86_64: error while loading state section id 1(block)
qemu-system-x86_64: load of migration failed: Invalid argument

Can you explain the id=disk1 on the master side?

Dave

> 
> Thanks
> Wen Congyang
> 
> > 
> > Dave
> > 
> >>
> >> Thanks
> >> Wen Congyang
> >>
> >>>
> >>> - Michael
> >>>
> >>> .
> >>>
> >>
> >>
> > --
> > Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
> > .
> > 
> 
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK