From: "Michael R. Hines" <mrhines@linux.vnet.ibm.com>
To: Hongyang Yang <yanghy@cn.fujitsu.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: FNST-Gui Jianfeng <GuiJianfeng@cn.fujitsu.com>,
Dong Eddie <eddie.dong@intel.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [RFC] COLO HA Project proposal
Date: Tue, 08 Jul 2014 14:06:14 +0800 [thread overview]
Message-ID: <53BB8A56.2050005@linux.vnet.ibm.com> (raw)
In-Reply-To: <53B4D133.4060903@cn.fujitsu.com>
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
next prev parent reply other threads:[~2014-07-08 6:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 2:08 [Qemu-devel] [RFC] COLO HA Project proposal Hongyang Yang
2014-07-01 12:12 ` Dr. David Alan Gilbert
2014-07-03 3:42 ` Hongyang Yang
2014-07-04 8:31 ` Dong, Eddie
2014-07-04 8:35 ` Dr. David Alan Gilbert
2014-07-04 8:54 ` Dong, Eddie
2014-07-04 12:22 ` Dr. David Alan Gilbert
2014-07-04 15:55 ` Dong, Eddie
2014-07-08 6:06 ` Michael R. Hines [this message]
2014-07-08 6:26 ` Hongyang Yang
2014-07-04 11:22 ` Andreas Färber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53BB8A56.2050005@linux.vnet.ibm.com \
--to=mrhines@linux.vnet.ibm.com \
--cc=GuiJianfeng@cn.fujitsu.com \
--cc=dgilbert@redhat.com \
--cc=eddie.dong@intel.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=yanghy@cn.fujitsu.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).