From: Stefan Hajnoczi <stefanha@gmail.com>
To: Jules Wang <junqing.wang@cs2c.com.cn>
Cc: pbonzini@redhat.com, quintela@redhat.com, qemu-devel@nongnu.org,
owasserm@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 1/4] Curling: add doc
Date: Thu, 17 Oct 2013 13:25:53 +0200 [thread overview]
Message-ID: <20131017112553.GE10774@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1381821983-13932-2-git-send-email-junqing.wang@cs2c.com.cn>
On Tue, Oct 15, 2013 at 03:26:20PM +0800, Jules Wang wrote:
> +Usage
> +=====
> +The steps of curling are the same as the steps of live migration except the
> +following:
> +1. Start ft in the qemu monitor of sender vm by following cmdline:
> + > migrate_set_speed <full bandwidth>
> + > migrate -f tcp:<address>:<port>
> +2. Connect to the receiver vm by vnc or spice. The screen of the vm is displayed
> +when ft is ready.
Management tools (like libvirt) need a QMP event that reports when FT is
active. This allows users to check the FT status of a guest and
understand when the guest is protected.
Stefan
next prev parent reply other threads:[~2013-10-17 11:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 7:26 [Qemu-devel] [PATCH v3 0/4] Curling: KVM Fault Tolerance Jules Wang
2013-10-15 7:26 ` [Qemu-devel] [PATCH v3 1/4] Curling: add doc Jules Wang
2013-10-17 11:25 ` Stefan Hajnoczi [this message]
2013-10-15 7:26 ` [Qemu-devel] [PATCH v3 2/4] Curling: cmdline interface Jules Wang
2013-10-15 7:26 ` [Qemu-devel] [PATCH v3 3/4] Curling: the sender Jules Wang
2013-10-15 7:26 ` [Qemu-devel] [PATCH v3 4/4] Curling: the receiver Jules Wang
2013-10-17 11:50 ` [Qemu-devel] [PATCH v3 0/4] Curling: KVM Fault Tolerance Stefan Hajnoczi
2013-10-23 0:08 ` Jules
2013-10-24 12:10 ` Stefan Hajnoczi
2013-10-22 21:00 ` Michael R. Hines
2013-10-23 5:23 ` Jules
2013-11-06 18:38 ` Michael R. Hines
2013-10-22 21:08 ` Michael R. Hines
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=20131017112553.GE10774@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=junqing.wang@cs2c.com.cn \
--cc=owasserm@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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).