qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [RFC PATCH v2 11/12] mc: introduce new capabilities to


From: Michael R. Hines
Subject: Re: [Qemu-devel] [RFC PATCH v2 11/12] mc: introduce new capabilities to control micro-checkpointing
Date: Fri, 04 Apr 2014 11:56:36 +0800
User-agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.4.0

On 03/12/2014 06:02 AM, Juan Quintela wrote:
address@hidden wrote:
From: "Michael R. Hines" <address@hidden>

New capabilities include the use of RDMA acceleration,
use of network buffering, and keepalive support, as documented
in patch #1.

Signed-off-by: Michael R. Hines <address@hidden>
---
  qapi-schema.json | 36 +++++++++++++++++++++++++++++++++++-
  1 file changed, 35 insertions(+), 1 deletion(-)

diff --git a/qapi-schema.json b/qapi-schema.json
index 98abdac..1fdf208 100644
--- a/qapi-schema.json
+++ b/qapi-schema.json
@@ -720,10 +720,44 @@
  # @auto-converge: If enabled, QEMU will automatically throttle down the guest
  #          to speed up convergence of RAM migration. (since 1.6)
  #
+# @mc: The migration will never end, and the VM will instead be continuously
+#          micro-checkpointed (MC). Use the command migrate-set-mc-delay to
+#          control the frequency at which the checkpoints occur.
+#          Disabled by default. (Since 2.x)
+#
+# @mc-net-disable: Deactivate network buffering against outbound network
+#          traffic while Micro-Checkpointing (@mc) is active.
+#          Enabled by default. Disabling will make the MC protocol inconsistent
+#          and potentially break network connections upon an actual failure.
+#          Only for performance testing. (Since 2.x)
If it is dangerous, can we put dangerous/unsafe on the name?  Having an option 
that
can corrupt things make me nervous.

You got it =)

- Michael




reply via email to

[Prev in Thread] Current Thread [Next in Thread]