zhanghailiang 5821ebf93b 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>		2016-10-30 15:17:39 +05:30
..
block.h	Clean up header guards that don't match their file name	2016-07-12 16:19:16 +02:00
colo.h	COLO: migrate COLO related info to secondary node	2016-10-30 15:17:39 +05:30
cpu.h	hw: move CPU state serialization to migration/cpu.h	2016-05-19 16:42:28 +02:00
migration.h	migration: Introduce capability 'x-colo' to migration	2016-10-30 15:17:39 +05:30
page_cache.h	xbzrle: optimize XBZRLE to decrease the cache misses	2015-01-15 17:49:43 +05:30
postcopy-ram.h	Postcopy: Mark nohugepage before discard	2015-11-10 15:00:28 +01:00
qemu-file.h	Clean up decorations and whitespace around header guards	2016-07-12 16:20:46 +02:00
qjson.h	migration/qjson: Drop gratuitous use of QOM	2016-05-23 14:16:12 +05:30
vmstate.h	Clean up decorations and whitespace around header guards	2016-07-12 16:20:46 +02:00