From: Anthony Liguori <aliguori@linux.vnet.ibm.com>
To: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
Luiz Capitulino <lcapitulino@redhat.com>,
qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>
Subject: [Qemu-devel] Re: [CFR 6/10] qmp: migrate command
Date: Wed, 16 Jun 2010 13:52:21 -0500 [thread overview]
Message-ID: <4C191D65.8060101@linux.vnet.ibm.com> (raw)
In-Reply-To: <1276703160-7894-7-git-send-email-stefanha@linux.vnet.ibm.com>
On 06/16/2010 10:45 AM, Stefan Hajnoczi wrote:
> migrate
> -------
>
> Migrate to URI.
>
This command will not be compatible with 0.14.
Regards,
Anthony Liguori
> Arguments:
>
> - "blk": block migration, full disk copy (json-bool, optional)
> - "inc": incremental disk copy (json-bool, optional)
> - "uri": Destination URI (json-string)
>
> Example:
>
> -> { "execute": "migrate", "arguments": { "uri": "tcp:0:4446" } }
> <- { "return": {} }
>
> Notes:
>
> (1) The 'query-migrate' command should be used to check migration's progress
> and final result (this information is provided by the 'status' member)
> (2) All boolean arguments default to false
> (3) The user Monitor's "detach" argument is invalid in QMP and should not
> be used
>
next prev parent reply other threads:[~2010-06-16 18:52 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-16 15:45 [Qemu-devel] [CFR 0/10] QMP specification review (Part 2) Stefan Hajnoczi
2010-06-16 15:45 ` [Qemu-devel] [CFR 1/10] qmp: getfd command Stefan Hajnoczi
2010-06-16 18:47 ` [Qemu-devel] " Anthony Liguori
2010-06-17 19:49 ` [Qemu-devel] " Stefan Hajnoczi
2010-06-16 15:45 ` [Qemu-devel] [CFR 2/10] qmp: memsave command Stefan Hajnoczi
2010-06-16 18:49 ` [Qemu-devel] " Anthony Liguori
2010-06-17 19:57 ` [Qemu-devel] " Stefan Hajnoczi
2010-06-16 15:45 ` [Qemu-devel] [CFR 3/10] qmp: migrate_cancel command Stefan Hajnoczi
2010-06-16 18:49 ` [Qemu-devel] " Anthony Liguori
2010-06-16 15:45 ` [Qemu-devel] [CFR 4/10] qmp: migrate_set_downtime command Stefan Hajnoczi
2010-06-16 18:50 ` [Qemu-devel] " Anthony Liguori
2010-06-17 19:59 ` [Qemu-devel] " Stefan Hajnoczi
2010-06-16 15:45 ` [Qemu-devel] [CFR 5/10] qmp: migrate_set_speed command Stefan Hajnoczi
2010-06-16 18:51 ` [Qemu-devel] " Anthony Liguori
2010-06-17 20:00 ` [Qemu-devel] " Stefan Hajnoczi
2010-06-16 15:45 ` [Qemu-devel] [CFR 6/10] qmp: migrate command Stefan Hajnoczi
2010-06-16 18:52 ` Anthony Liguori [this message]
2010-06-16 15:45 ` [Qemu-devel] [CFR 7/10] qmp: netdev_add command Stefan Hajnoczi
2010-06-16 18:53 ` [Qemu-devel] " Anthony Liguori
2010-06-16 15:45 ` [Qemu-devel] [CFR 8/10] qmp: netdev_del command Stefan Hajnoczi
2010-06-16 18:53 ` [Qemu-devel] " Anthony Liguori
2010-06-17 20:01 ` [Qemu-devel] " Stefan Hajnoczi
2010-06-16 15:45 ` [Qemu-devel] [CFR 9/10] qmp: pmemsave command Stefan Hajnoczi
2010-06-16 18:53 ` [Qemu-devel] " Anthony Liguori
2010-06-16 15:46 ` [Qemu-devel] [CFR 10/10] qmp: query_balloon command Stefan Hajnoczi
2010-06-16 18:54 ` [Qemu-devel] " Anthony Liguori
2010-06-17 20:03 ` Stefan Hajnoczi
2010-06-16 18:12 ` [Qemu-devel] [CFR 0/10] QMP specification review (Part 2) Blue Swirl
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=4C191D65.8060101@linux.vnet.ibm.com \
--to=aliguori@linux.vnet.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=armbru@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.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).