From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Michael R. Hines" Subject: Re: [Qemu-devel] [RFC] COLO HA Project proposal Date: Tue, 08 Jul 2014 14:06:14 +0800 Message-ID: <53BB8A56.2050005@linux.vnet.ibm.com> References: <53A8DD80.7070905@cn.fujitsu.com> <20140701121248.GH2394@work-vm> <53B4D133.4060903@cn.fujitsu.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FNST-Gui Jianfeng , Dong Eddie , qemu-devel@nongnu.org, kvm@vger.kernel.org To: Hongyang Yang , "Dr. David Alan Gilbert" Return-path: Received: from e8.ny.us.ibm.com ([32.97.182.138]:44953 "EHLO e8.ny.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752630AbaGHGGW (ORCPT ); Tue, 8 Jul 2014 02:06:22 -0400 Received: from /spool/local by e8.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Tue, 8 Jul 2014 02:06:22 -0400 Received: from b01cxnp23034.gho.pok.ibm.com (b01cxnp23034.gho.pok.ibm.com [9.57.198.29]) by d01dlp03.pok.ibm.com (Postfix) with ESMTP id 89425C90026 for ; Tue, 8 Jul 2014 02:06:13 -0400 (EDT) Received: from d01av04.pok.ibm.com (d01av04.pok.ibm.com [9.56.224.64]) by b01cxnp23034.gho.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id s6866JxL2162944 for ; Tue, 8 Jul 2014 06:06:19 GMT Received: from d01av04.pok.ibm.com (localhost [127.0.0.1]) by d01av04.pok.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id s6866JP4002803 for ; Tue, 8 Jul 2014 02:06:19 -0400 In-Reply-To: <53B4D133.4060903@cn.fujitsu.com> Sender: kvm-owner@vger.kernel.org List-ID: On 07/03/2014 11:42 AM, Hongyang Yang wrote: > >> I wonder if there is anyway to coordinate this between COLO, Michael >> Hines microcheckpointing and the two separate reverse-execution >> projects that also need to do some similar things. >> Are there any standard APIs for the heartbeet thing we can already >> tie into? > > Sadly we have checked MC, it does not have heartbeat support for now. > Right, MC by itself does not need heartbeats out-of-the box. Probably the best thing we can coordinate from MC is the part of the data transmission protocol and memory management - because we need to make sure you guys are staying compatible with the QEMUFile abstraction the same way that the TCP and RDMA protocols are staying compatible with that abstraction. COLO should able to run over any protocol supported by QEMUFile. I can help with some of that... - Michael