Commit c2eb7f21 authored by Greg Kurz's avatar Greg Kurz Committed by Dr. David Alan Gilbert
Browse files

migration: improve documentation of postcopy-ram 



This capability must have the same value on both source and destination,
otherwise migration fails (commit 875fcd01 "migration: incoming
postcopy advise sanity checks").

Let's write it down in various places where postcopy-ram is documented.

Signed-off-by: default avatarGreg Kurz <groug@kaod.org>
Message-Id: <151801810352.29167.4832480228518630626.stgit@bahia.lan>
Signed-off-by: default avatarDr. David Alan Gilbert <dgilbert@redhat.com>
Reviewed-by: default avatarEric Blake <eblake@redhat.com>
Reviewed-by: default avatarDr. David Alan Gilbert <dgilbert@redhat.com>
parent 96994fd1

docs/devel/migration.rst

+2 −2
Original line number Diff line number Diff line
@@ -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``

hmp-commands.hx

+2 −1
Original line number Diff line number Diff line
@@ -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,

    },

qapi/migration.json

+6 −4
Original line number Diff line number Diff line
@@ -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

#