From: Luiz Capitulino <lcapitulino@redhat.com>
To: aliguori@us.ibm.com
Cc: Jan Kiszka <jan.kiszka@siemens.com>, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 3/3] Reset system before loadvm
Date: Tue, 21 Jun 2011 14:57:28 -0300 [thread overview]
Message-ID: <1308679048-4441-4-git-send-email-lcapitulino@redhat.com> (raw)
In-Reply-To: <1308679048-4441-1-git-send-email-lcapitulino@redhat.com>
From: Jan Kiszka <jan.kiszka@siemens.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 | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/savevm.c b/savevm.c
index 939845c..8139bc7 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);
--
1.7.6.rc2.11.g13b7
next prev parent reply other threads:[~2011-06-21 17:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 17:57 [Qemu-devel] [PULL 0/3]: Monitor queue Luiz Capitulino
2011-06-21 17:57 ` [Qemu-devel] [PATCH 1/3] error framework: Fix compilation for w32/w64 Luiz Capitulino
2011-06-21 17:57 ` [Qemu-devel] [PATCH 2/3] Allow silent system resets Luiz Capitulino
2011-06-21 17:57 ` Luiz Capitulino [this message]
2011-06-22 12:56 ` [Qemu-devel] [PULL 0/3]: Monitor queue Anthony Liguori
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1308679048-4441-4-git-send-email-lcapitulino@redhat.com \
--to=lcapitulino@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=jan.kiszka@siemens.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).