If there are file write operations in the guest when doing live migration, the VM downtime will be much longer than the max_downtime, this is caused by bdrv_flush_all(), this function is a time consuming operation if there a lot of data have to be flushed to disk.
By adding bdrv_flush_all() before VM stop, we can reduce the time consumed by bdrv_flush_all() in vm_stop_force_state, this means the VM down time can be reduced. The test shows this optimization can help to reduce the VM downtime from more than 20 seconds to about 100 milliseconds. Signed-off-by: Liang Li <[email protected]> --- migration/migration.c | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/migration/migration.c b/migration/migration.c index 2c805f1..fc4735c 100644 --- a/migration/migration.c +++ b/migration/migration.c @@ -655,6 +655,10 @@ static void *migration_thread(void *opaque) qemu_system_wakeup_request(QEMU_WAKEUP_REASON_OTHER); old_vm_running = runstate_is_running(); + /* do flush here is aimed to shorten the VM downtime, + * bdrv_flush_all is a time consuming operation + * when the guest has done some file writing */ + bdrv_flush_all(); ret = vm_stop_force_state(RUN_STATE_FINISH_MIGRATE); if (ret >= 0) { qemu_file_set_rate_limit(s->file, INT64_MAX); -- 1.9.1
