QEMU 4.0.0 and newer automatically drops caches at the end of migration,
which means we can safely allow migration even if disk/driver/@cache is
not none nor directsync.
Jiri Denemark (3):
qemu: Clarify error message in qemuMigrationSrcIsSafe
qemu: Check for drop-cache capability
qemu: Allow migration with disk cache on
src/qemu/qemu_capabilities.c | 2 ++
src/qemu/qemu_capabilities.h | 1 +
src/qemu/qemu_migration.c | 14 +++++++++++---
tests/qemucapabilitiesdata/caps_4.0.0.aarch64.xml | 1 +
tests/qemucapabilitiesdata/caps_4.0.0.ppc64.xml | 1 +
tests/qemucapabilitiesdata/caps_4.0.0.riscv32.xml | 1 +
tests/qemucapabilitiesdata/caps_4.0.0.riscv64.xml | 1 +
tests/qemucapabilitiesdata/caps_4.0.0.s390x.xml | 1 +
tests/qemucapabilitiesdata/caps_4.0.0.x86_64.xml | 1 +
tests/qemucapabilitiesdata/caps_4.1.0.x86_64.xml | 1 +
10 files changed, 21 insertions(+), 3 deletions(-)
--
2.22.1