qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	Ryan Harper <ryanh@us.ibm.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH][RESEND] Add monitor command for system_reboot
Date: Wed, 08 Jul 2009 16:11:46 +0300	[thread overview]
Message-ID: <4A549B12.9020503@redhat.com> (raw)
In-Reply-To: <4A549A0F.5040902@codemonkey.ws>

On 07/08/2009 04:07 PM, Anthony Liguori wrote:
> Avi Kivity wrote:
>> On 07/07/2009 10:26 PM, Ryan Harper wrote:
>>> Add a new monitor command (system_reboot) for a soft reboot which uses
>>> system_powerdown to trigger ACPI shutdown in the guest and once 
>>> shutdown
>>> is complete, trigger a reset instead of exiting qemu.
>>>
>>> Depends on commit a6d6552426dcbf726e5549f08b70c9318d6be14b which 
>>> enabled
>>> ACPI power button support.
>>>
>>> V2:
>>>      -added reset handler to lower the reboot flag on reset.
>>>
>>> Tested with:
>>>      - Ubuntu 9.04 64-bit guest.
>>>      - SLES 10 SP2 32-bit guest.
>>>      - RHEL 5.3 32 and 64 bit guests.
>>>
>>
>> I think a combination of system_powerdown, avoiding exit on shutdown, 
>> and system_reset is more flexible as it allows the controller to 
>> modify the guest before rebooting it.
>
> You need notification that the shutdown has occurred.  That's the only 
> bit we're missing today.  It's still not perfect though.
>
> libvirt does system_powerdown, guest completely ignores it, user 
> decides to power off, libvirt cannot tell the difference between user 
> requested power off and ACPI driven power down.

Does the patch handle this case?

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

  reply	other threads:[~2009-07-08 13:09 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-07 19:26 [Qemu-devel] [PATCH][RESEND] Add monitor command for system_reboot Ryan Harper
2009-07-08  5:06 ` Avi Kivity
2009-07-08 13:07   ` Anthony Liguori
2009-07-08 13:11     ` Avi Kivity [this message]
2009-07-08 13:16       ` Anthony Liguori
2009-07-08 13:28         ` Avi Kivity
2009-07-08  7:56 ` Gleb Natapov
2009-07-08 13:05   ` Anthony Liguori
2009-07-08 13:26     ` Daniel P. Berrange
2009-07-08 13:47       ` Anthony Liguori
2009-07-08 13:56         ` Daniel P. Berrange
2009-07-08 13:59           ` Anthony Liguori
2009-07-08 15:43           ` Ryan Harper
2009-07-08 15:49             ` Anthony Liguori
2009-07-08 15:58               ` Ryan Harper
2009-07-08 16:02                 ` Anthony Liguori
2009-07-08 16:02             ` Avi Kivity
2009-07-16  8:58               ` Amit Shah
2009-07-16 14:39                 ` Jamie Lokier
2009-07-16 14:49                   ` Amit Shah
2009-07-08 13:49     ` Gleb Natapov
2009-07-08 14:04     ` Avi Kivity
2009-07-08 14:10       ` Daniel P. Berrange
2009-07-08 15:16         ` Avi Kivity
2009-07-08 15:47           ` Stefano Stabellini
2009-07-08 15:54             ` Daniel P. Berrange
2009-07-08 15:59               ` Stefano Stabellini

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=4A549B12.9020503@redhat.com \
    --to=avi@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=anthony@codemonkey.ws \
    --cc=qemu-devel@nongnu.org \
    --cc=ryanh@us.ibm.com \
    /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).