From: James Thomason <james@divide.org>
To: "Jan C. Bernauer" <jan.bernauer@t-online.de>, <kvm@vger.kernel.org>
Subject: Re: BUG: Guest lockup and 100% CPU load on host
Date: Thu, 15 Jan 2009 15:00:08 -0800 [thread overview]
Message-ID: <C594FFF8.625D%james@divide.org> (raw)
In-Reply-To: <496FB451.3020002@t-online.de>
Jan,
I spent some time with the same problem over the last two days. Avi Kivity
suggested adding "clocksource=acpi_pm" to the guest kernel boot line, and
that seems to have resolved the issue. Would you give that a try and let me
know the result? Also I believe the following bugs might be related:
[ 2351676 ] Guests hang periodically on Ubuntu-8.10
[ 2353811 ] Solaris 10 guest unstable
[ 2494730 ] Guests "stalling" on kvm-82
[ 2138079 ] kvm locks up system
[ 2113643 ] guests AND host still getting stuck under CPU load
Regards,
James
On 1/15/09 2:10 PM, "Jan C. Bernauer" <jan.bernauer@t-online.de> wrote:
> Hi,
>
> while I was trying to get pci passthrough to work without vt-d using
> the 1to1 mapping (it works ;),
> I stumbled upon a solid lock up of the guest.
> (Unpatched source shows the same behaviour)
>
> I see a strange look up of the guest OS with the following "features":
> - guest doesn't respond anymore
> - triggered by load in the guest.
> - it seems it is easier to trigger with -smp 2
> - host shows qemu process with 100% cpu
> - seems to be cured by --no-kvm-irqchip
> - --no-kvm-pit does not help
> - qmeu console command system_reset works
>
> Right now, guest OS is linux 2.6.27.1
> Latest KVM from git, host is 2.6.28.
> Older kvms seem to exhibit the same problem.
next prev parent reply other threads:[~2009-01-15 23:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-15 22:10 BUG: Guest lockup and 100% CPU load on host Jan C. Bernauer
2009-01-15 23:00 ` James Thomason [this message]
2009-01-16 10:13 ` Jan Bernauer
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=C594FFF8.625D%james@divide.org \
--to=james@divide.org \
--cc=jan.bernauer@t-online.de \
--cc=kvm@vger.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 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.