From c2eb7f213a15b870f7a35ec961e4f1e0f7e2df91 Mon Sep 17 00:00:00 2001 From: Greg Kurz Date: Wed, 7 Feb 2018 16:41:43 +0100 Subject: migration: improve documentation of postcopy-ram 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 Message-Id: <151801810352.29167.4832480228518630626.stgit@bahia.lan> Signed-off-by: Dr. David Alan Gilbert Reviewed-by: Eric Blake Reviewed-by: Dr. David Alan Gilbert --- qapi/migration.json | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) (limited to 'qapi') diff --git a/qapi/migration.json b/qapi/migration.json index 4cd3d13158..7f465a1902 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 # -- cgit v1.2.3