From: Jan Bernauer <bernauer@kph.uni-mainz.de>
To: kvm@vger.kernel.org
Subject: Re: BUG: Guest lockup and 100% CPU load on host
Date: Fri, 16 Jan 2009 11:13:11 +0100 [thread overview]
Message-ID: <49705DB7.8020900@kph.uni-mainz.de> (raw)
In-Reply-To: <C594FFF8.625D%james@divide.org>
Hi,
thanks for the info! It seems quite stable now, but I haven't tried
-smp 2 yet.
Timing problems seem plausible: I have a dvb-card passed through to the
guest. With normal setup, the frontend detection of the driver module
breaks every other try with a i2c timeout.
I changed the cpufreq governor of the host from ondemand to performance,
and the guest seemed stable, until suddenly the timeouts filled the logs
again.
Until now, with clocksource=acpi_pm, I saw only occasional irq timeouts
of the card (like, under 10 in 30 minutes), under heavy load of the guest.
James Thomason wrote:
> 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
>
Best regards,
Jan
--
Jan C. Bernauer email: bernauer@kph.uni-mainz.de
Institut für Kernphysik tel : 06131 - 39 25826
Johannes-Gutenberg-Universität Mainz fax : 06131 - 39 22964
Johann-Joachim-Becher-Weg 45
55099 Mainz
prev parent reply other threads:[~2009-01-16 10:22 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
2009-01-16 10:13 ` Jan Bernauer [this message]
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=49705DB7.8020900@kph.uni-mainz.de \
--to=bernauer@kph.uni-mainz.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox