aad555c229
We need to know if migration is going into COLO state for incoming side before start normal migration. Instead by using the VMStateDescription to send colo_state from source side to destination side, we use MIG_CMD_ENABLE_COLO to indicate whether COLO is enabled or not. Signed-off-by: zhanghailiang <zhang.zhanghailiang@huawei.com> Signed-off-by: Zhang Chen <zhangckid@gmail.com> Signed-off-by: Zhang Chen <chen.zhang@intel.com> Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com> Signed-off-by: Jason Wang <jasowang@redhat.com>
16 lines
484 B
Makefile
16 lines
484 B
Makefile
common-obj-y += migration.o socket.o fd.o exec.o
|
|
common-obj-y += tls.o channel.o savevm.o
|
|
common-obj-y += colo.o colo-failover.o
|
|
common-obj-y += vmstate.o vmstate-types.o page_cache.o
|
|
common-obj-y += qemu-file.o global_state.o
|
|
common-obj-y += qemu-file-channel.o
|
|
common-obj-y += xbzrle.o postcopy-ram.o
|
|
common-obj-y += qjson.o
|
|
common-obj-y += block-dirty-bitmap.o
|
|
|
|
common-obj-$(CONFIG_RDMA) += rdma.o
|
|
|
|
common-obj-$(CONFIG_LIVE_BLOCK_MIGRATION) += block.o
|
|
|
|
rdma.o-libs := $(RDMA_LIBS)
|