From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:39706) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VYj45-0000Z4-Cb for qemu-devel@nongnu.org; Tue, 22 Oct 2013 17:00:42 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VYj3w-0007PN-Ed for qemu-devel@nongnu.org; Tue, 22 Oct 2013 17:00:33 -0400 Received: from e9.ny.us.ibm.com ([32.97.182.139]:60391) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VYj3w-0007Ni-B5 for qemu-devel@nongnu.org; Tue, 22 Oct 2013 17:00:24 -0400 Received: from /spool/local by e9.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Tue, 22 Oct 2013 17:00:23 -0400 Received: from b01cxnp22036.gho.pok.ibm.com (b01cxnp22036.gho.pok.ibm.com [9.57.198.26]) by d01dlp01.pok.ibm.com (Postfix) with ESMTP id 13A0C38C8054 for ; Tue, 22 Oct 2013 17:00:19 -0400 (EDT) Received: from d03av03.boulder.ibm.com (d03av03.boulder.ibm.com [9.17.195.169]) by b01cxnp22036.gho.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r9ML0JpT66257112 for ; Tue, 22 Oct 2013 21:00:19 GMT Received: from d03av03.boulder.ibm.com (localhost [127.0.0.1]) by d03av03.boulder.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id r9ML0IrB009853 for ; Tue, 22 Oct 2013 15:00:19 -0600 Message-ID: <5266E75F.9060300@linux.vnet.ibm.com> Date: Tue, 22 Oct 2013 17:00:15 -0400 From: "Michael R. Hines" MIME-Version: 1.0 References: <1381821983-13932-1-git-send-email-junqing.wang@cs2c.com.cn> In-Reply-To: <1381821983-13932-1-git-send-email-junqing.wang@cs2c.com.cn> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v3 0/4] Curling: KVM Fault Tolerance List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jules Wang Cc: pbonzini@redhat.com, Juan Jose Quintela Carreira , "Michael R. Hines" , qemu-devel@nongnu.org, owasserm@redhat.com On 10/15/2013 03:26 AM, Jules Wang wrote: > v2 -> v3: > * add documentation of new option in qapi-schema. > > * long option name: ft -> fault-tolerant > > v1 -> v2: > * cmdline: migrate curling:tcp:
: > -> migrate -f tcp:
: > > * sender: use QEMU_VM_FILE_MAGIC_FT as the header of the migration > to indicate this is a ft migration. > > * receiver: look for the signature: > QEMU_VM_EOF_MAGIC + QEMU_VM_FILE_MAGIC_FT(64bit total) > which indicates the end of one migration. > -- > Jules Wang (4): > Curling: add doc > Curling: cmdline interface. > Curling: the sender > Curling: the receiver > > arch_init.c | 25 ++++-- > docs/curling.txt | 51 ++++++++++++ > hmp-commands.hx | 10 ++- > hmp.c | 3 +- > include/migration/migration.h | 1 + > include/migration/qemu-file.h | 1 + > include/sysemu/sysemu.h | 5 +- > migration.c | 50 ++++++++++-- > qapi-schema.json | 6 +- > qmp-commands.hx | 3 +- > savevm.c | 178 +++++++++++++++++++++++++++++++++++++++--- > 11 files changed, 303 insertions(+), 30 deletions(-) > create mode 100644 docs/curling.txt > Jules, I think we should work together. The patches I sent this week solve all of the problems (and more) of Kemari and have been in testing for over 1 year. 1. I/O buffering is already working 2. Checkpoint parallelism is already working 3. Staging of the checkpoint memory is already working on both the sender side and receiver side. 3. Checkpoint chunking is already working (this means that checkpoints can be very large and must be split up like slab caches, which can dynamically grow and shrink as the amount of diryt memory in the virtual machine fluctuates. 4. RDMA checkpointing is already working 5. TCP checkpointing is already working 6. There does not need to be a custom migration URI - this is easily implemented through a capability. 7. Libvirt support is already available on github. 8 There is no need to modify the QEMU migration metadata state information. All of these features take advantage of the recent advances in QEMU in migration performance improvements over the last few years. Would you be interested in "joining forces"? You even picked a cool name (I didn't even choose a name)..... =) Also: I will soon be working in IBM China Beijing, for 3 years - starting next month - perhaps we could talk on the phone (or meet in person)? - Michael