From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56899) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bzHEB-00014L-5u for qemu-devel@nongnu.org; Wed, 26 Oct 2016 01:58:20 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bzHE7-0008Fb-5A for qemu-devel@nongnu.org; Wed, 26 Oct 2016 01:58:19 -0400 Received: from mx1.redhat.com ([209.132.183.28]:55104) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1bzHE6-0008FV-Vg for qemu-devel@nongnu.org; Wed, 26 Oct 2016 01:58:15 -0400 Date: Wed, 26 Oct 2016 11:28:10 +0530 From: Amit Shah Message-ID: <20161026055810.GN1679@amit-lp.rh> References: <1476792613-11712-1-git-send-email-zhang.zhanghailiang@huawei.com> <1476792613-11712-15-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-15-git-send-email-zhang.zhanghailiang@huawei.com> Subject: Re: [Qemu-devel] [PATCH COLO-Frame (Base) v21 14/17] COLO: Implement the process of failover for primary VM 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 On (Tue) 18 Oct 2016 [20:10:10], zhanghailiang wrote: > For primary side, if COLO gets failover request from users. > To be exact, gets 'x_colo_lost_heartbeat' command. > COLO thread will exit the loop while the failover BH does the > cleanup work and resumes VM. > > Signed-off-by: zhanghailiang > Signed-off-by: Li Zhijian > Reviewed-by: Dr. David Alan Gilbert > @@ -162,9 +196,20 @@ static int colo_do_checkpoint_transaction(MigrationState *s, > @@ -280,8 +330,6 @@ out: > if (local_err) { > error_report_err(local_err); > } > - migrate_set_state(&s->state, MIGRATION_STATUS_COLO, > - MIGRATION_STATUS_COMPLETED); Yea, I guess this should not have been done in the previous patch to begin with? Amit