From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: ACPI weirdness with SVN head
Date: Sun, 08 Feb 2009 08:41:54 -0600 [thread overview]
Message-ID: <498EEF32.6070004@codemonkey.ws> (raw)
In-Reply-To: <498ED10F.2020600@web.de>
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
>
>
next prev parent reply other threads:[~2009-02-08 14:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-08 10:36 [Qemu-devel] ACPI weirdness with SVN head Erik de Castro Lopo
2009-02-08 11:05 ` Erik de Castro Lopo
2009-02-08 12:33 ` [Qemu-devel] " Jan Kiszka
2009-02-08 14:41 ` Anthony Liguori [this message]
2009-02-09 0:54 ` Erik de Castro Lopo
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=498EEF32.6070004@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=qemu-devel@nongnu.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.