From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1LclwK-0006Cn-Nj
	for qemu-devel@nongnu.org; Thu, 26 Feb 2009 14:30:36 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1LclwJ-0006Cb-7F
	for qemu-devel@nongnu.org; Thu, 26 Feb 2009 14:30:36 -0500
Received: from [199.232.76.173] (port=44412 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1LclwJ-0006CY-3O
	for qemu-devel@nongnu.org; Thu, 26 Feb 2009 14:30:35 -0500
Received: from mail-bw0-f171.google.com ([209.85.218.171]:34683)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <blauwirbel@gmail.com>) id 1LclwI-0000ur-L8
	for qemu-devel@nongnu.org; Thu, 26 Feb 2009 14:30:34 -0500
Received: by bwz19 with SMTP id 19so622541bwz.34
	for <qemu-devel@nongnu.org>; Thu, 26 Feb 2009 11:30:33 -0800 (PST)
MIME-Version: 1.0
In-Reply-To: <20090226135521.GA14001@amd.home.annexia.org>
References: <20090225233718.GA15750@amd.home.annexia.org>
	<20090226105106.GD22494@redhat.com>
	<20090226135521.GA14001@amd.home.annexia.org>
Date: Thu, 26 Feb 2009 21:30:33 +0200
Message-ID: <f43fc5580902261130m6ebbc204wc80e04a8eea04c8e@mail.gmail.com>
Subject: Re: [Qemu-devel] Hardware watchdogs (patch for discussion only)
From: Blue Swirl <blauwirbel@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.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.