qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Juan Quintela <quintela@redhat.com>, qemu-devel@nongnu.org
Cc: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] [PULL 02/11] Add migrate_incoming
Date: Mon, 16 Mar 2015 08:35:09 -0600	[thread overview]
Message-ID: <5506EA1D.70805@redhat.com> (raw)
In-Reply-To: <1426513272-20070-3-git-send-email-quintela@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 977 bytes --]

On 03/16/2015 07:41 AM, Juan Quintela wrote:
> From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
> 
> Add migrate_incoming/migrate-incoming to start an incoming
> migration.
> 
> Once a qemu has been started with
>     -incoming defer
> 
> the migration can be started by issuing:
>     migrate_incoming uri
> 
> Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> Reviewed-by: Eric Blake <eblake@redhat.com>
> Signed-off-by: Juan Quintela <quintela@redhat.com>
> ---

> +-> { "execute": "migrate-incoming", "arguments": { "uri": "tcp::4446" } }
> +<- { "return": {} }
> +
> +Notes:
> +
> +(1) QEMU must be started with -incoming defer to allow migrate-incoming to
> +    be used
> +(2) The uri format is the same as to -incoming

Minor grammar issue (could be fixed in a followup): would read better with:

s/as to/as for/

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]

  reply	other threads:[~2015-03-16 14:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-16 13:41 [Qemu-devel] [PULL 00/11] Migration pull request Juan Quintela
2015-03-16 13:41 ` [Qemu-devel] [PULL 01/11] Add -incoming defer Juan Quintela
2015-03-16 13:41 ` [Qemu-devel] [PULL 02/11] Add migrate_incoming Juan Quintela
2015-03-16 14:35   ` Eric Blake [this message]
2015-03-16 13:41 ` [Qemu-devel] [PULL 03/11] ram: make all save_page functions take a uint64_t parameter Juan Quintela
2015-03-16 13:41 ` [Qemu-devel] [PULL 04/11] ram_find_and_save_block: change calling convention Juan Quintela
2015-03-16 13:41 ` [Qemu-devel] [PULL 05/11] ram_save_page: change calling covention Juan Quintela
2015-03-16 13:41 ` [Qemu-devel] [PULL 06/11] save_xbzrle_page: change calling convention Juan Quintela
2015-03-16 13:41 ` [Qemu-devel] [PULL 07/11] save_block_hdr: we can recalculate the cont parameter here Juan Quintela
2015-03-17  3:13   ` Li, Liang Z
2015-03-17 12:00     ` Juan Quintela
2015-03-16 13:41 ` [Qemu-devel] [PULL 08/11] rename save_block_hdr to save_page_header Juan Quintela
2015-03-16 13:41 ` [Qemu-devel] [PULL 09/11] migration: Read JSON VM description on incoming migration Juan Quintela
2015-03-16 13:41 ` [Qemu-devel] [PULL 10/11] migration: Allow to suppress vmdesc submission Juan Quintela
2015-03-16 13:41 ` [Qemu-devel] [PULL 11/11] pc: Disable vmdesc submission for old machines Juan Quintela
2015-03-16 15:55 ` [Qemu-devel] [PULL 00/11] Migration pull request Markus Armbruster
2015-03-16 16:20   ` Juan Quintela
2015-03-16 17:22 ` Peter Maydell

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=5506EA1D.70805@redhat.com \
    --to=eblake@redhat.com \
    --cc=dgilbert@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).