From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1LWArS-0001h7-Ro
	for qemu-devel@nongnu.org; Sun, 08 Feb 2009 09:42:18 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1LWArR-0001fC-Vt
	for qemu-devel@nongnu.org; Sun, 08 Feb 2009 09:42:18 -0500
Received: from [199.232.76.173] (port=42082 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1LWArR-0001f2-RN
	for qemu-devel@nongnu.org; Sun, 08 Feb 2009 09:42:17 -0500
Received: from yw-out-1718.google.com ([74.125.46.158]:59700)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <anthony@codemonkey.ws>) id 1LWArR-00078Y-GQ
	for qemu-devel@nongnu.org; Sun, 08 Feb 2009 09:42:17 -0500
Received: by yw-out-1718.google.com with SMTP id 6so325904ywa.82
	for <qemu-devel@nongnu.org>; Sun, 08 Feb 2009 06:42:16 -0800 (PST)
Message-ID: <498EEF32.6070004@codemonkey.ws>
Date: Sun, 08 Feb 2009 08:41:54 -0600
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Re: ACPI weirdness with  SVN head
References: <20090208213637.e76e8fd7.mle+tools@mega-nerd.com>	<20090208220520.6b3238ac.mle+tools@mega-nerd.com>
	<498ED10F.2020600@web.de>
In-Reply-To: <498ED10F.2020600@web.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

Jan Kiszka wrote:
> Erik de Castro Lopo wrote:
>   
>> Erik de Castro Lopo wrote:
>>
>>     
>>> Is this a known problem?
>>>       
>> More info. If I disable ACPI with -no-acpi the VM boots but
>>  then chews up far more of the host CPU than previously. The
>> only real explanation I can find for this on the guest side
>> is a very high number of timer interrupts:
>>
>>     guest > cat /proc/interrupts 
>>                CPU0       
>>       0:    2575369    XT-PIC-XT        timer
>>       1:          9    XT-PIC-XT        i8042
>>       2:          0    XT-PIC-XT        cascade
>>       4:        536    XT-PIC-XT        serial
>>       8:          0    XT-PIC-XT        rtc0
>>       9:          0    XT-PIC-XT        virtio0
>>      11:        202    XT-PIC-XT        virtio1, eth0
>>      12:        111    XT-PIC-XT        i8042
>>      14:       4176    XT-PIC-XT        ata_piix
>>      15:       3676    XT-PIC-XT        ata_piix
>>     NMI:          0   Non-maskable interrupts
>>     LOC:          0   Local timer interrupts
>>     RES:          0   Rescheduling interrupts
>>     CAL:          0   function call interrupts
>>     TLB:          0   TLB shootdowns
>>     TRM:          0   Thermal event interrupts
>>     THR:          0   Threshold APIC interrupts
>>     SPU:          0   Spurious interrupts
>>     ERR:          0
>>
>> Cheers,
>> Erik
>>     
>
> I stumbled over the same problem with one of my Linux guests [1], but as
> the one that locked up was built without CONFIG_ACPI, I concluded that
> this is the problem (it missed that pin1 became 2, just like your guest
> does). Have you updated your BIOS image?
>   

This error happens if you're using an older version of the BIOS.

Regards,

Anthony Liguori

> Jan
>
> [1] http://comments.gmane.org/gmane.comp.emulators.qemu/37767
>
>