qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: Jan Kiszka <jan.kiszka@web.de>,
	qemu-devel <qemu-devel@nongnu.org>,
	Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] [RFC] Introduce vm_stop_permanent()
Date: Thu, 28 Jul 2011 10:23:22 +0300	[thread overview]
Message-ID: <4E310E6A.6000004@redhat.com> (raw)
In-Reply-To: <CAAu8pHv7PO=Zc5arNaTPhcXj+BDgtkieOxTQqaFO6pmA1PYfwQ@mail.gmail.com>

On 07/28/2011 12:44 AM, Blue Swirl wrote:
> On Wed, Jul 27, 2011 at 9:42 PM, Luiz Capitulino<lcapitulino@redhat.com>  wrote:
> >  This function should be used when the VM is not supposed to resume
> >  execution (eg. by issuing 'cont' monitor command).
> >
> >  Today, we allow the user to resume execution even when:
> >
> >    o the guest shuts down and -no-shutdown is used
> >    o there's a kvm internal error
> >    o loading the VM state with -loadvm or "loadvm" in the monitor fails
> >
> >  I think only badness can happen from the cases above.
>
> I'd suppose a system_reset should bring the system back to sanity and
> then clear vm_permanent_stopped (where's -ly?) except maybe for KVM
> internal error if that can't be recovered. Then it would not very
> permanent anymore, so the name would need adjusting.

Currently, all kvm internal errors are recoverable by reset (and 
possibly by fiddling with memory/registers).

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

  reply	other threads:[~2011-07-28  7:23 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-27 18:42 [Qemu-devel] [RFC] Introduce vm_stop_permanent() Luiz Capitulino
2011-07-27 21:44 ` Blue Swirl
2011-07-28  7:23   ` Avi Kivity [this message]
2011-07-28 13:31     ` Luiz Capitulino
2011-07-28 13:37       ` Avi Kivity
2011-07-28 14:19         ` Jan Kiszka
2011-07-28 15:18           ` Luiz Capitulino
2011-07-28 15:20             ` Jan Kiszka
2011-07-28 17:39               ` Luiz Capitulino
2011-07-28 17:48                 ` Luiz Capitulino
2011-07-28 17:52                   ` Jan Kiszka
2011-07-28 18:00                     ` Luiz Capitulino
2011-07-28 18:04                       ` Jan Kiszka
2011-07-28 18:22                         ` Luiz Capitulino
2011-07-28 18:28                           ` Alon Levy
2011-07-30  7:41                           ` Blue Swirl
2011-08-01 12:46                             ` Luiz Capitulino
2011-08-02 10:22       ` Daniel P. Berrange
2011-08-02 19:07         ` Luiz Capitulino

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=4E310E6A.6000004@redhat.com \
    --to=avi@redhat.com \
    --cc=blauwirbel@gmail.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).