qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: qemu-devel <qemu-devel@nongnu.org>,
	Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] Reset system before loadvm
Date: Tue, 14 Jun 2011 13:50:39 +0300	[thread overview]
Message-ID: <4DF73CFF.3070403@redhat.com> (raw)
In-Reply-To: <4DF6FD6D.6020109@web.de>

On 06/14/2011 09:19 AM, Jan Kiszka wrote:
> On 2011-06-12 19:13, Avi Kivity wrote:
> >  On 06/11/2011 12:05 PM, Jan Kiszka wrote:
> >>  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. Almost no device takes care of
> >>  this scenario.
> >>
> >>  However, fixing this is trivial. We just need to issue a system reset
> >>  during loadvm as well.
>

> >>  +    qemu_system_reset();
> >>        ret = qemu_loadvm_state(f);
> >>
> >>        qemu_fclose(f);
> >
> >  Should we suppress the reset event sent out on the monitor?  After all,
> >  it's the result of an internal implementation choice, not something the
> >  user or the guest did.
>
> We already issue this pattern during -loadvm or -incoming - or is the
> monitor not yet connected at this point?

I believe it is not.  But regardless, we shouldn't add more incorrect 
behaviour.

-- 
error compiling committee.c: too many arguments to function

  reply	other threads:[~2011-06-14 10:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-11  9:05 [Qemu-devel] [PATCH] Reset system before loadvm Jan Kiszka
2011-06-12 17:13 ` Avi Kivity
2011-06-14  6:19   ` Jan Kiszka
2011-06-14 10:50     ` Avi Kivity [this message]
2011-06-14 10:56       ` Jan Kiszka
2011-06-14 11:14         ` Avi Kivity
2011-06-14 15:45           ` Luiz Capitulino
2011-06-12 17:42 ` Peter Maydell
2011-06-14  6:16   ` Jan Kiszka
2011-06-14 16:29 ` [Qemu-devel] [PATCH 1/2] Allow silent system resets Jan Kiszka
2011-06-15 14:32   ` Luiz Capitulino
2011-06-14 16:29 ` [Qemu-devel] [PATCH v2 2/2] Reset system before loadvm Jan Kiszka

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=4DF73CFF.3070403@redhat.com \
    --to=avi@redhat.com \
    --cc=jan.kiszka@web.de \
    --cc=lcapitulino@redhat.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).