summaryrefslogtreecommitdiff
path: root/savevm.c
diff options
context:
space:
mode:
authorMichael S. Tsirkin <mst@redhat.com>2010-11-22 19:52:26 +0200
committerMichael S. Tsirkin <mst@redhat.com>2010-12-09 12:47:48 +0200
commiteff06c40d330cdbea414331337ca6f5032dbf6d7 (patch)
tree9eb5bdab8f011ba0e70da12373e08e0241c89029 /savevm.c
parent55df6f33655ed4139c824aa3ab9a4ab0c19dca83 (diff)
downloadqemu-eff06c40d330cdbea414331337ca6f5032dbf6d7.zip
migration/savevm: no need to flush requests
There's no need to flush requests after vmstop as vmstop does it for us automatically now. Signed-off-by: Michael S. Tsirkin <mst@redhat.com> Tested-by: Jason Wang <jasowang@redhat.com>
Diffstat (limited to 'savevm.c')
-rw-r--r--savevm.c4
1 files changed, 0 insertions, 4 deletions
diff --git a/savevm.c b/savevm.c
index d38f79e6bd..90aa237c9c 100644
--- a/savevm.c
+++ b/savevm.c
@@ -1575,8 +1575,6 @@ static int qemu_savevm_state(Monitor *mon, QEMUFile *f)
saved_vm_running = vm_running;
vm_stop(0);
- bdrv_flush_all();
-
ret = qemu_savevm_state_begin(mon, f, 0, 0);
if (ret < 0)
goto out;
@@ -1885,8 +1883,6 @@ void do_savevm(Monitor *mon, const QDict *qdict)
monitor_printf(mon, "No block device can accept snapshots\n");
return;
}
- /* ??? Should this occur after vm_stop? */
- qemu_aio_flush();
saved_vm_running = vm_running;
vm_stop(0);