From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:37681)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <stefanha@redhat.com>) id 1Z7OTZ-0001lO-Om
	for qemu-devel@nongnu.org; Tue, 23 Jun 2015 09:43:02 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <stefanha@redhat.com>) id 1Z7OTU-0004tf-SE
	for qemu-devel@nongnu.org; Tue, 23 Jun 2015 09:42:57 -0400
Date: Tue, 23 Jun 2015 14:42:43 +0100
From: Stefan Hajnoczi <stefanha@redhat.com>
Message-ID: <20150623134243.GA31481@stefanha-thinkpad.redhat.com>
References: <1434617361-17778-1-git-send-email-wency@cn.fujitsu.com>
	<1434617361-17778-8-git-send-email-wency@cn.fujitsu.com>
	<20150618125533.GE25387@stefanha-thinkpad.redhat.com>
	<5582D777.8060202@gmail.com>
	<20150618160618.GF822@stefanha-thinkpad.redhat.com>
	<55836860.2010401@cn.fujitsu.com>
	<20150619104953.GB9807@stefanha-thinkpad.redhat.com>
	<5584DEA8.80005@gmail.com>
	<20150622123935.GB783@stefanha-thinkpad.redhat.com>
	<55881408.20506@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="ZPt4rx8FFjLCG7dd"
Content-Disposition: inline
In-Reply-To: <55881408.20506@gmail.com>
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH COLO-Block v6 07/16] Add new
 block driver interface to connect/disconnect the remote target
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 <ghostwcy@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Fam Zheng <famz@redhat.com>, Lai Jiangshan <laijs@cn.fujitsu.com>, qemu block <qemu-block@nongnu.org>, Stefan Hajnoczi <stefanha@gmail.com>, Jiang Yunhong <yunhong.jiang@intel.com>, Dong Eddie <eddie.dong@intel.com>, qemu devel <qemu-devel@nongnu.org>, Max Reitz <mreitz@redhat.com>, Gonglei <arei.gonglei@huawei.com>, Paolo Bonzini <pbonzini@redhat.com>, Yang Hongyang <yanghy@cn.fujitsu.com>, "Dr. David Alan Gilbert" <dgilbert@redhat.com>, zhanghailiang <zhang.zhanghailiang@huawei.com>


--ZPt4rx8FFjLCG7dd
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Jun 22, 2015 at 09:56:24PM +0800, Wen Congyang wrote:
> >The NBD connect should not be performed during downtime, regardless of
> >whether a monitor command is used or not.
>=20
> Why?

NBD connection establishment takes unbounded time.  It can extend the
downtime period and cause users to notice that the guest is unavailable.

The point of COLO is fault tolerance and high availability.  In order to
achieve that, COLO must minimize downtime.  If an operation can be
performed outside the migration downtime phase, then it should be done
outside.

Stefan

--ZPt4rx8FFjLCG7dd
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJViWJTAAoJEJykq7OBq3PICbQIAJN3U9Q3G6O+k6W5qdrPMsGH
0dPdVXnxr5i2q9YphDCGN3aQ98aD2HeMWrC/4TSbX8xZwMxM7m075yQTKgraae3Q
xgC04+Inw3aUS8NOhxn71bKvBLA2Z5vRYb5Bg7pJXzdlU74H8K9DwwwelP0scGZA
gl/Eg2eT6Sy52e/uYfhBmyXCtX9tGe6gufoX+W1AvXRcpayVLBFG7j3ERNrs3wzF
xIAp7Aw2Blgd9cveaXfSnkpQrbdX4ffl6uiuno4yy5h1yjOCw03pWViyy6vo/oBT
savHYMyZR/JNoOoYfqiDjwX6S04bYQyM4bLGI6+NlEB8y1+0RX3KpgmWo25WmPI=
=vZjO
-----END PGP SIGNATURE-----

--ZPt4rx8FFjLCG7dd--