| commit | 5a8a49d7aa78b31a853e8f5d31f5b12811caeb27 | |
| author | Jan Kiszka <jan.kiszka@siemens.com> | |
| Tue, 14 Jun 2011 16:29:45 +0000 (14 18:29 +0200) | ||
| committer | Luiz Capitulino <lcapitulino@redhat.com> | |
| Thu, 16 Jun 2011 14:42:40 +0000 (16 11:42 -0300) | ||
| tree | d37d14601537b65a8235724214faa06cfaf91c59 | treesnapshot (tar.gz zip) |
| parent | e063eb1f4a6d42371e7d288dfdb690d5821190ed | commitdiff |
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>
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>
| savevm.c | diffblobblamehistory |