From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:42634) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bzFvy-0006sD-Bi for qemu-devel@nongnu.org; Wed, 26 Oct 2016 00:35:27 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bzFvu-0000M9-5F for qemu-devel@nongnu.org; Wed, 26 Oct 2016 00:35:26 -0400 Received: from mx1.redhat.com ([209.132.183.28]:52270) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1bzFvt-0000LE-WB for qemu-devel@nongnu.org; Wed, 26 Oct 2016 00:35:22 -0400 Date: Wed, 26 Oct 2016 10:05:17 +0530 From: Amit Shah Message-ID: <20161026043517.GB1679@amit-lp.rh> References: <1476792613-11712-1-git-send-email-zhang.zhanghailiang@huawei.com> <1476792613-11712-3-git-send-email-zhang.zhanghailiang@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1476792613-11712-3-git-send-email-zhang.zhanghailiang@huawei.com> Subject: Re: [Qemu-devel] [PATCH COLO-Frame (Base) v21 02/17] COLO: migrate COLO related info to secondary node List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: zhanghailiang Cc: quintela@redhat.com, qemu-devel@nongnu.org, dgilbert@redhat.com, wency@cn.fujitsu.com, lizhijian@cn.fujitsu.com, xiecl.fnst@cn.fujitsu.com, Gonglei On (Tue) 18 Oct 2016 [20:09:58], zhanghailiang wrote: > We can determine whether or not VM in destination should go into COLO mode > by referring to the info that was migrated. > > We skip this section if COLO is not enabled (i.e. > migrate_set_capability colo off), so that, It doesn't break compatibility > with migration no matter whether users configure the --enable-colo/disable-colo > on the source/destination side or not; > > Signed-off-by: zhanghailiang > Signed-off-by: Li Zhijian > Signed-off-by: Gonglei > Reviewed-by: Dr. David Alan Gilbert Reviewed-by: Amit Shah Amit