From: Gleb Natapov <gleb@redhat.com>
To: Cyrill Gorcunov <gorcunov@gmail.com>
Cc: Pekka Enberg <penberg@kernel.org>, Amos Kong <akong@redhat.com>,
kvm@vger.kernel.org, Asias He <asias.hejun@gmail.com>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: kvm tools: rhel6.0 guest hung during shutdown
Date: Mon, 11 Apr 2011 22:32:37 +0300 [thread overview]
Message-ID: <20110411193237.GB21604@redhat.com> (raw)
In-Reply-To: <4DA35656.8070608@gmail.com>
On Mon, Apr 11, 2011 at 11:28:22PM +0400, Cyrill Gorcunov wrote:
> On 04/11/2011 11:07 PM, Gleb Natapov wrote:
> > On Mon, Apr 11, 2011 at 10:01:30PM +0300, Pekka Enberg wrote:
> >> On Sun, 2011-04-10 at 16:58 +0300, Gleb Natapov wrote:
> >>> On Sun, Apr 10, 2011 at 09:49:31PM +0800, Amos Kong wrote:
> >>>> System halted.
> >>>> [note: guest hung .......]
> >>>>
> >>> Isn't that expected result without ACPI support? I would expect all guests
> >>> to hang like that at the end.
> >>
> >> I see hangs with Debian Squeeze image too but not with the minimal QEMU
> >> image I usually test things with. I wonder, though, why userspace
> >> insists on using ACPI for shutdown as we boot with 'noapic'.
> >>
> > There is not way to power down PC from software without ACPI (may be APM
> > has something, but I doubt kvm-tool implements it either). Do you remember
> > Windows 95 "it is now safe to turn off your computer" screen?
>
> yup, iirc APM had some set power state entry point, but not sure, need to find docs ;)
>
Just go for ACPI then. APM is dead.
--
Gleb.
prev parent reply other threads:[~2011-04-11 19:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-10 13:49 kvm tools: rhel6.0 guest hung during shutdown Amos Kong
2011-04-10 13:58 ` Gleb Natapov
2011-04-11 19:01 ` Pekka Enberg
2011-04-11 19:07 ` Gleb Natapov
2011-04-11 19:28 ` Cyrill Gorcunov
2011-04-11 19:32 ` Gleb Natapov [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=20110411193237.GB21604@redhat.com \
--to=gleb@redhat.com \
--cc=akong@redhat.com \
--cc=asias.hejun@gmail.com \
--cc=gorcunov@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@kernel.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