v2: - One more patch: "migration: Make migration blocker work for snapshots too" - Move register of migration blocker to be before dump_init [Marc-Andre] - Collected r-bs
Both dump-guest-memory and live migration have vm state cached internally. Allowing them to happen together means the vm state can be messed up. Simply block live migration for dump-guest-memory. One trivial thing to mention is we should still allow dump-guest-memory even if -only-migratable is specified, because that flag should majorly be used to guarantee not adding devices that will block migration by accident. Dump guest memory is not like that - it'll only block for the seconds when it's dumping. Thanks, Peter Xu (3): migration: Make migration blocker work for snapshots too migration: Add migrate_add_blocker_internal() dump-guest-memory: Block live migration dump/dump.c | 24 +++++++++++++++++++----- include/migration/blocker.h | 16 ++++++++++++++++ migration/migration.c | 24 +++++++++++++++--------- 3 files changed, 50 insertions(+), 14 deletions(-) -- 2.31.1
