5821ebf93b
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>
15 lines
352 B
Makefile
15 lines
352 B
Makefile
common-obj-y += migration.o socket.o fd.o exec.o
|
|
common-obj-y += tls.o
|
|
common-obj-$(CONFIG_COLO) += colo.o
|
|
common-obj-y += colo-comm.o
|
|
common-obj-y += vmstate.o
|
|
common-obj-y += qemu-file.o
|
|
common-obj-y += qemu-file-channel.o
|
|
common-obj-y += xbzrle.o postcopy-ram.o
|
|
common-obj-y += qjson.o
|
|
|
|
common-obj-$(CONFIG_RDMA) += rdma.o
|
|
|
|
common-obj-y += block.o
|
|
|