qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Greg Kurz <groug@kaod.org>
Cc: qemu-devel@nongnu.org, Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] migration: improve documentation of postcopy-ram
Date: Wed, 7 Feb 2018 15:55:01 +0000	[thread overview]
Message-ID: <20180207155500.GO2665@work-vm> (raw)
In-Reply-To: <151801810352.29167.4832480228518630626.stgit@bahia.lan>

* Greg Kurz (groug@kaod.org) wrote:
> This capability must have the same value on both source and destination,
> otherwise migration fails (commit 875fcd013ab6 "migration: incoming
> postcopy advise sanity checks").
> 
> Let's write it down in various places where postcopy-ram is documented.
> 
> Signed-off-by: Greg Kurz <groug@kaod.org>

Thanks,

Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>

> ---
>  docs/devel/migration.rst |    4 ++--
>  hmp-commands.hx          |    3 ++-
>  qapi/migration.json      |   10 ++++++----
>  3 files changed, 10 insertions(+), 7 deletions(-)
> 
> diff --git a/docs/devel/migration.rst b/docs/devel/migration.rst
> index bf97080dac2f..9d1b7657f0cf 100644
> --- a/docs/devel/migration.rst
> +++ b/docs/devel/migration.rst
> @@ -387,8 +387,8 @@ doesn't finish in a given time the switch is made to postcopy.
>  Enabling postcopy
>  -----------------
>  
> -To enable postcopy, issue this command on the monitor prior to the
> -start of migration:
> +To enable postcopy, issue this command on the monitor (both source and
> +destination) prior to the start of migration:
>  
>  ``migrate_set_capability postcopy-ram on``
>  
> diff --git a/hmp-commands.hx b/hmp-commands.hx
> index 15620c94d3fc..d26eb4119b9d 100644
> --- a/hmp-commands.hx
> +++ b/hmp-commands.hx
> @@ -1041,7 +1041,8 @@ ETEXI
>          .params     = "",
>          .help       = "Followup to a migration command to switch the migration"
>                        " to postcopy mode. The postcopy-ram capability must "
> -                      "be set before the original migration command.",
> +                      "be set on both source and destination before the "
> +                      "original migration command .",
>          .cmd        = hmp_migrate_start_postcopy,
>      },
>  
> diff --git a/qapi/migration.json b/qapi/migration.json
> index 4cd3d1315884..7f465a1902ce 100644
> --- a/qapi/migration.json
> +++ b/qapi/migration.json
> @@ -327,8 +327,10 @@
>  #          to speed up convergence of RAM migration. (since 1.6)
>  #
>  # @postcopy-ram: Start executing on the migration target before all of RAM has
> -#          been migrated, pulling the remaining pages along as needed. NOTE: If
> -#          the migration fails during postcopy the VM will fail.  (since 2.6)
> +#          been migrated, pulling the remaining pages along as needed. The
> +#          capacity must have the same setting on both source and target
> +#          or migration will not even start. NOTE: If the migration fails during
> +#          postcopy the VM will fail.  (since 2.6)
>  #
>  # @x-colo: If enabled, migration will never end, and the state of the VM on the
>  #        primary side will be migrated continuously to the VM on secondary
> @@ -742,8 +744,8 @@
>  # @migrate-start-postcopy:
>  #
>  # Followup to a migration command to switch the migration to postcopy mode.
> -# The postcopy-ram capability must be set before the original migration
> -# command.
> +# The postcopy-ram capability must be set on both source and destination
> +# before the original migration command.
>  #
>  # Since: 2.5
>  #
> 
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

  parent reply	other threads:[~2018-02-07 15:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-07 15:41 [Qemu-devel] [PATCH] migration: improve documentation of postcopy-ram Greg Kurz
2018-02-07 15:47 ` Eric Blake
2018-02-07 15:55 ` Dr. David Alan Gilbert [this message]
2018-02-14  9:44   ` Greg Kurz
2018-02-14  9:45     ` Dr. David Alan Gilbert
2018-02-14  9:55       ` Greg Kurz

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=20180207155500.GO2665@work-vm \
    --to=dgilbert@redhat.com \
    --cc=groug@kaod.org \
    --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).