summaryrefslogtreecommitdiff
path: root/include/migration/colo.h
diff options
context:
space:
mode:
authorzhanghailiang <zhang.zhanghailiang@huawei.com>2016-10-27 14:42:53 +0800
committerAmit Shah <amit@amitshah.net>2016-10-30 15:17:39 +0530
commit5821ebf93b1da9f74dc04c20e2923aadfaf803df (patch)
treef9bf82c835185d3404eebb0e775c81d2d56b97bf /include/migration/colo.h
parent35a6ed4f716c1027c04d12a3c499b2e9d6b62c24 (diff)
downloadqemu-5821ebf93b1da9f74dc04c20e2923aadfaf803df.zip
COLO: migrate COLO related info to secondary node
We can determine whether or not VM in destination should go into COLO mode by referring to the info that was migrated. We skip this section if COLO is not enabled (i.e. migrate_set_capability colo off), so that, It doesn't break compatibility with migration no matter whether users configure the --enable-colo/disable-colo on the source/destination side or not; Signed-off-by: zhanghailiang <zhang.zhanghailiang@huawei.com> Signed-off-by: Li Zhijian <lizhijian@cn.fujitsu.com> Signed-off-by: Gonglei <arei.gonglei@huawei.com> Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com> Reviewed-by: Amit Shah <amit.shah@redhat.com> Signed-off-by: Amit Shah <amit@amitshah.net>
Diffstat (limited to 'include/migration/colo.h')
-rw-r--r--include/migration/colo.h2
1 files changed, 2 insertions, 0 deletions
diff --git a/include/migration/colo.h b/include/migration/colo.h
index 59a632a418..1c899a0bc4 100644
--- a/include/migration/colo.h
+++ b/include/migration/colo.h
@@ -14,7 +14,9 @@
#define QEMU_COLO_H
#include "qemu-common.h"
+#include "migration/migration.h"
bool colo_supported(void);
+void colo_info_init(void);
#endif