summaryrefslogtreecommitdiff
path: root/savevm.c
diff options
context:
space:
mode:
authorJan Kiszka <jan.kiszka@siemens.com>2011-06-14 18:29:45 +0200
committerLuiz Capitulino <lcapitulino@redhat.com>2011-06-16 11:42:40 -0300
commit5a8a49d7aa78b31a853e8f5d31f5b12811caeb27 (patch)
treed37d14601537b65a8235724214faa06cfaf91c59 /savevm.c
parente063eb1f4a6d42371e7d288dfdb690d5821190ed (diff)
downloadqemu-5a8a49d7aa78b31a853e8f5d31f5b12811caeb27.tar.gz
Reset system before loadvm
In case we load the vmstate during incoming migration, we start from a clean, default machine state as we went through system reset before. But if we load from a snapshot, the machine can be in any state. That can cause troubles if loading an older image which does not carry all state information the executing QEMU requires. Hardly any device takes care of this scenario. However, fixing this is trivial. We just need to issue a system reset during loadvm as well. Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com> Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
Diffstat (limited to 'savevm.c')
-rw-r--r--savevm.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/savevm.c b/savevm.c
index 939845c825..8139bc7e29 100644
--- a/savevm.c
+++ b/savevm.c
@@ -2073,6 +2073,7 @@ int load_vmstate(const char *name)
return -EINVAL;
}
+ qemu_system_reset(VMRESET_SILENT);
ret = qemu_loadvm_state(f);
qemu_fclose(f);