From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:56900)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1ZCP68-0005BK-Qb
	for qemu-devel@nongnu.org; Tue, 07 Jul 2015 05:23:29 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1ZCP68-0005mV-3R
	for qemu-devel@nongnu.org; Tue, 07 Jul 2015 05:23:28 -0400
References: <1435635285-5804-1-git-send-email-wency@cn.fujitsu.com>
	<20150703153011.GD2142@work-vm> <5597D5BA.6030500@gmail.com>
	<559B1C92.90400@linux.vnet.ibm.com> <559B2669.8050509@cn.fujitsu.com>
	<20150707091323.GC2347@work-vm>
From: Paolo Bonzini <pbonzini@redhat.com>
Message-ID: <559B9A80.5080901@redhat.com>
Date: Tue, 7 Jul 2015 11:23:12 +0200
MIME-Version: 1.0
In-Reply-To: <20150707091323.GC2347@work-vm>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
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: "Dr. David Alan Gilbert" <dgilbert@redhat.com>, 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>, Stefan Hajnoczi <stefanha@redhat.com>, Yang Hongyang <yanghy@cn.fujitsu.com>, Lai Jiangshan <laijs@cn.fujitsu.com>



On 07/07/2015 11:13, Dr. David Alan Gilbert wrote:
>> > This log is very stange. The NBD client connects to NBD server, and NBD server wants to read data
>> > from NBD client, but reading fails. It seems that the connection is closed unexpectedly. Can you
>> > give me more log and how do you use it?
> That was the same failure I was getting.   I think it's that the NBD server and client are in different
> modes, with one of them expecting the export.

nbd_server_add always expects the export.

Paolo