qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Blue Swirl <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Hardware watchdogs (patch for discussion only)
Date: Thu, 26 Feb 2009 21:30:33 +0200	[thread overview]
Message-ID: <f43fc5580902261130m6ebbc204wc80e04a8eea04c8e@mail.gmail.com> (raw)
In-Reply-To: <20090226135521.GA14001@amd.home.annexia.org>

On 2/26/09, Richard W.M. Jones <rjones@redhat.com> wrote:
> On Thu, Feb 26, 2009 at 10:51:06AM +0000, Daniel P. Berrange wrote:
>  > I think we can only support the following options
>  >
>  >  - shutdown - graceful shutdown of guest via ACPI event via
>  >               qemu_system_powerdown_request()
>  >  - poweroff - hard immediate power off of guest machine via
>  >               qemu_system_shutdown_request()
>  >  - reset    - hard reset of the guest machine via
>  >               qemu_system_reset_request()
>  >  - pause    - stop the guest CPU(s)
>
>
> Thanks.
>
>  My experiments show that qemu_system_powerdown_request does nothing
>  visible, even for a recent (F-10) guest running acpid.
>  "system_powerdown" in the monitor also does nothing for the same
>  guest.  Maybe this is a recent regression in QEMU?

It's only implemented on Sparc32 and even there Linux does not have a
driver for the power fail interrupt. The idea was that power supply,
power button press or UPS would notify the OS that power will fail and
the system should be shut down.

On Sparc32 actually the power fail interrupt doesn't exactly indicate
what I thought it does, there are two power supplies and the other one
may fail but system can still be running for a long time.

  reply	other threads:[~2009-02-26 19:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-25 23:37 [Qemu-devel] Hardware watchdogs (patch for discussion only) Richard W.M. Jones
2009-02-26 10:51 ` Daniel P. Berrange
2009-02-26 13:55   ` Richard W.M. Jones
2009-02-26 19:30     ` Blue Swirl [this message]
2009-02-26 14:31   ` Steve Fosdick
2009-02-26 14:45     ` Richard W.M. Jones
2009-02-27  9:55       ` Steve Fosdick
2009-02-26 17:50     ` Jamie Lokier
2009-02-27  9:50       ` Steve Fosdick
2009-02-27 12:19         ` Paul Brook
2009-02-28 21:34           ` Jamie Lokier
2009-02-28 22:00             ` Andreas Färber
2009-02-28 22:11           ` Richard W.M. Jones

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=f43fc5580902261130m6ebbc204wc80e04a8eea04c8e@mail.gmail.com \
    --to=blauwirbel@gmail.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).