diff options
| author | Kevin Wolf <kwolf@redhat.com> | 2013-07-18 14:52:19 +0200 |
|---|---|---|
| committer | Stefan Hajnoczi <stefanha@redhat.com> | 2013-07-19 12:29:21 +0800 |
| commit | 594a45ce64dbef1829996403506a1154eb2fd1cc (patch) | |
| tree | f18db8a1b7dc695eef70a37c6f73c1c3794230e6 /block.c | |
| parent | 323004a39d4d8d33c744a5b108f80bfe6402fca3 (diff) | |
cpus: Let vm_stop[_force_state]() always flush block devices
Even if the VM is already stopped, we cannot assume that all data has
already been successfully flushed to disk. The flush during the previous
vm_stop() could have failed.
Run bdrv_flush_all() unconditionally so that we get an error each time
if the block device isn't really flushed.
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Diffstat (limited to 'block.c')
0 files changed, 0 insertions, 0 deletions