All of lore.kernel.org
 help / color / mirror / Atom feed
From: "François Revol" <revol@free.fr>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] wake-on-lan & IPMI implementation; real power-off and -no-shutdown
Date: Tue, 16 Mar 2010 15:26:14 +0100 CET	[thread overview]
Message-ID: <869578612-BeMail@laptop> (raw)
In-Reply-To: <20100316105358.0831df27@redhat.com>

> > > Also, it seems -no-shutdown doesn't actually "stop the emulation"
> > > as
> > > said in the manual, it actually keeps the vm running (and using
> > > cpu),
> > > despite the OS trying to shutdown via ACPI. At least I tested so
> > > with
> > > Haiku (and acpi=true in kernel config), which properly exits QEMU
> > > without -no-shutdown.
> >
> > Hmm, I think -no-shutdown should at least stop the CPUs executing.
> > It is
> > not really useful on its own though. The app managing QEMU would
> > want to
> > use the new JSON based monitor to listen for the SHUTDOWN event to
> > be
> > emitted, so it can detect the shutdown completing & then take
> > action it
> > wants either reset the guest, or kill QEMU, etc
>
>  If I'm not missing something, -no-shutdown calls vm_stop(), which
> calls
> pause_all_vcpus().

Oh indeed, "info status" shows the VM as "paused".
I was misled because the GUI window was still open...

François.

      reply	other threads:[~2010-03-16 14:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-15 15:01 [Qemu-devel] wake-on-lan & IPMI implementation; real power-off and -no-shutdown François Revol
2010-03-15 15:26 ` Paul Brook
2010-03-15 15:37   ` François Revol
2010-03-15 15:51     ` Anthony Liguori
2010-03-15 16:00       ` François Revol
2010-03-15 15:55 ` Daniel P. Berrange
2010-03-15 16:29   ` Anthony Liguori
2010-03-15 16:36     ` François Revol
2010-03-16 17:28     ` Jamie Lokier
2010-03-16 17:44       ` Daniel P. Berrange
2010-03-16 18:22       ` François Revol
2010-03-16 13:53   ` Luiz Capitulino
2010-03-16 14:26     ` François Revol [this message]

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=869578612-BeMail@laptop \
    --to=revol@free.fr \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.