From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: David Brown <dmlb2000-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: ACPI issue with F8 guest
Date: Mon, 26 Nov 2007 18:51:53 +0200 [thread overview]
Message-ID: <474AF9A9.1050905@qumranet.com> (raw)
In-Reply-To: <9c21eeae0711260817r1d5955bbv1ca1d879bd99f3e3-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
David Brown wrote:
> For some reason acpi refuses to start on a Fedora 8 guest. The dmesg
> says at the very begining "no DMI BIOS year, acpi=force is required to
> enable ACPI". I then put acpi=force on the command line and it
> sometimes works and sometimes doesn't. What I mean by works is
> sometimes it issues the acpi shutdown command and halts qemu and
> sometimes I have to kill the process, and all I see on dmesg is
> "Halting system...\nSystem halted." It seems like after I login to
> gnome in the guest (and it starts allocating memory for gnome) then
> open up a gnome-terminal and halt the guest it doesn't work but if I
> don't go into X at all it works fine.... odd.
>
>
Known issue (cause not yet identified).
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2007-11-26 16:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-26 16:17 ACPI issue with F8 guest David Brown
[not found] ` <9c21eeae0711260817r1d5955bbv1ca1d879bd99f3e3-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-11-26 16:51 ` Avi Kivity [this message]
[not found] ` <474AF9A9.1050905-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-11-26 16:52 ` David Brown
[not found] ` <9c21eeae0711260852j4d6e4a55i6b9e32358dc8cc6f-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-11-26 17:02 ` Avi Kivity
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=474AF9A9.1050905@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=dmlb2000-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.