From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GXXn3-0007zj-7y for qemu-devel@nongnu.org; Wed, 11 Oct 2006 02:42:05 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GXXn1-0007vg-5u for qemu-devel@nongnu.org; Wed, 11 Oct 2006 02:42:04 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GXXn0-0007vQ-Vt for qemu-devel@nongnu.org; Wed, 11 Oct 2006 02:42:03 -0400 Received: from [203.190.192.17] (helo=wasp.net.au) by monty-python.gnu.org with esmtp (Exim 4.52) id 1GXXux-0001jO-9X for qemu-devel@nongnu.org; Wed, 11 Oct 2006 02:50:15 -0400 Message-ID: <452C9219.4070300@wasp.net.au> Date: Wed, 11 Oct 2006 10:41:29 +0400 From: Brad Campbell MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Windows, acpi and kqemu Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org G'day all. Has anyone managed to get Win2k or XP reliably running with acpi and kqemu? I get random errors usually related to memory access according to the blue screens. Without ACPI it runs ok.. and without kqemu it runs ok. I can not (and I've been trying hard) managed to reproduce any problems using a linux guest yet. I did notice that the linux guests disable the pmtimer as being bogus and moan about the base address for the SM controller being uninitialised, but I've not had the time to try and chase this down. Brad -- "Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so." -- Douglas Adams