qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Ryan Harper <ryanh@us.ibm.com>,
	qemu-devel@nongnu.org, Gleb Natapov <gleb@redhat.com>
Subject: Re: [Qemu-devel] [PATCH][RESEND] Add monitor command for system_reboot
Date: Wed, 8 Jul 2009 14:26:23 +0100	[thread overview]
Message-ID: <20090708132623.GN26640@redhat.com> (raw)
In-Reply-To: <4A549990.2060205@us.ibm.com>

On Wed, Jul 08, 2009 at 08:05:20AM -0500, Anthony Liguori wrote:
> Gleb Natapov wrote:
> >On Tue, Jul 07, 2009 at 02:26:31PM -0500, 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.
> >>    
> >OS is free to ignore ACPI shutdown request and in this case
> >reboot_requested will not be reset. On the next user initiated
> >guest power down qemu will reboot instead of exit.
> >  
> 
> Indeed.  This is what has kept me from applying this but I just can't 
> think of any better solution.
> 
> Any ideas?

Only other option I think of is a pure paravirt shutdown/reboot
handler, ala Xen. That sucks in different ways though, namely
needing a driver in the guest, which is probably worse.


Daniel
-- 
|: Red Hat, Engineering, London   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|

  reply	other threads:[~2009-07-08 13:36 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
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 [this message]
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=20090708132623.GN26640@redhat.com \
    --to=berrange@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=gleb@redhat.com \
    --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).