summaryrefslogtreecommitdiffstats
path: root/migration/migration.c
diff options
context:
space:
mode:
authorRao, Lei2021-06-08 10:23:28 +0200
committerJason Wang2021-06-11 04:30:13 +0200
commit3ba024457facdb6b0ef9c5c742261d4080a80a11 (patch)
tree381771eb6d52d507aeee4b50de203a7afeec7398 /migration/migration.c
parentOptimize the function of filter_send (diff)
downloadqemu-3ba024457facdb6b0ef9c5c742261d4080a80a11.tar.gz
qemu-3ba024457facdb6b0ef9c5c742261d4080a80a11.tar.xz
qemu-3ba024457facdb6b0ef9c5c742261d4080a80a11.zip
Remove migrate_set_block_enabled in checkpoint
We can detect disk migration in migrate_prepare, if disk migration is enabled in COLO mode, we can directly report an error.and there is no need to disable block migration at every checkpoint. Signed-off-by: Lei Rao <lei.rao@intel.com> Signed-off-by: Zhang Chen <chen.zhang@intel.com> Reviewed-by: Li Zhijian <lizhijian@fujitsu.com> Reviewed-by: Zhang Chen <chen.zhang@intel.com> Reviewed-by: Lukas Straub <lukasstraub2@web.de> Tested-by: Lukas Straub <lukasstraub2@web.de> Signed-off-by: Jason Wang <jasowang@redhat.com>
Diffstat (limited to 'migration/migration.c')
-rw-r--r--migration/migration.c4
1 files changed, 4 insertions, 0 deletions
diff --git a/migration/migration.c b/migration/migration.c
index 393299e150..4828997f63 100644
--- a/migration/migration.c
+++ b/migration/migration.c
@@ -2217,6 +2217,10 @@ static bool migrate_prepare(MigrationState *s, bool blk, bool blk_inc,
}
if (blk || blk_inc) {
+ if (migrate_colo_enabled()) {
+ error_setg(errp, "No disk migration is required in COLO mode");
+ return false;
+ }
if (migrate_use_block() || migrate_use_block_incremental()) {
error_setg(errp, "Command options are incompatible with "
"current migration capabilities");