summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorzhanghailiang <zhang.zhanghailiang@huawei.com>2016-11-02 15:44:12 +0800
committerLaurent Vivier <laurent@vivier.eu>2016-11-17 08:52:47 +0100
commit252093a726eb8aefdea13544554c24f7704555b4 (patch)
tree792efa27d1adcf89a95cf468171addf3386f04e6
parentb0bcc86d2a87456f5a276f941dc775b265b309cf (diff)
downloadqemu-252093a726eb8aefdea13544554c24f7704555b4.tar.gz
qapi-schema: clarify 'colo' state for MigrationStatus
VM can not get into colo state unless users enable 'x-colo' capability for migration, Here it is necessary to clarify this. Suggested-by: Eric Blake <eblake@redhat.com> Signed-off-by: zhanghailiang <zhang.zhanghailiang@huawei.com> Message-Id: <1478072652-9884-1-git-send-email-zhang.zhanghailiang@huawei.com> Reviewed-by: Eric Blake <eblake@redhat.com> Signed-off-by: Laurent Vivier <laurent@vivier.eu>
-rw-r--r--qapi-schema.json8
1 files changed, 5 insertions, 3 deletions
diff --git a/qapi-schema.json b/qapi-schema.json
index b0b4bf64cc..f3e9bfc510 100644
--- a/qapi-schema.json
+++ b/qapi-schema.json
@@ -176,8 +176,9 @@
#
# @guest-panicked: guest has been panicked as a result of guest OS panic
#
-# @colo: guest is paused to save/restore VM state under colo checkpoint (since
-# 2.8)
+# @colo: guest is paused to save/restore VM state under colo checkpoint,
+# VM can not get into this state unless colo capability is enabled
+# for migration. (since 2.8)
##
{ 'enum': 'RunState',
'data': [ 'debug', 'inmigrate', 'internal-error', 'io-error', 'paused',
@@ -462,7 +463,8 @@
#
# @failed: some error occurred during migration process.
#
-# @colo: VM is in the process of fault tolerance. (since 2.8)
+# @colo: VM is in the process of fault tolerance, VM can not get into this
+# state unless colo capability is enabled for migration. (since 2.8)
#
# Since: 2.3
#