Commit 252093a7 authored by zhanghailiang's avatar zhanghailiang Committed by Laurent Vivier
Browse files

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: default avatarEric Blake <eblake@redhat.com>
Signed-off-by: default avatarzhanghailiang <zhang.zhanghailiang@huawei.com>
Message-Id: <1478072652-9884-1-git-send-email-zhang.zhanghailiang@huawei.com>
Reviewed-by: default avatarEric Blake <eblake@redhat.com>
Signed-off-by: default avatarLaurent Vivier <laurent@vivier.eu>
parent b0bcc86d

qapi-schema.json

+5 −3
Original line number Diff line number Diff line
@@ -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

#