From: Avi Kivity <avi@redhat.com>
To: James Thomason <james@divide.org>
Cc: kvm@vger.kernel.org
Subject: Re: Guest Hang Bugs
Date: Thu, 15 Jan 2009 17:27:39 +0200 [thread overview]
Message-ID: <496F55EB.6040506@redhat.com> (raw)
In-Reply-To: <C5937A33.61B6%james@divide.org>
James Thomason wrote:
> Hello,
>
> I am able to reliably reproduce a condition where a guest goes into a tight
> loop or spinlock on all running cores. The scenario is exactly as described
> in bug 2351676, though my environment differs as detailed below. My
> observation is that the issue is correlated to the number of VCPUs assigned
> to the guest and CPU load. The higher the number of VCPUs and CPU
> utilization, the more easily it is triggered. If a KVM developer is
> interested in debugging live, I might be able to arrange getting the system
> in question into a DMZ. A review of the kvm tracker leads me to believe
> that the following bugs are possibly 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
>
>
Cam you try adding clocksource=acpi_pm to the _guest_ kernel command line?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-01-15 15:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 19:17 Guest Hang Bugs James Thomason
2009-01-15 15:27 ` Avi Kivity [this message]
2009-01-15 22:49 ` James Thomason
2009-01-16 1:26 ` James Thomason
2009-01-18 9:15 ` Avi Kivity
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=496F55EB.6040506@redhat.com \
--to=avi@redhat.com \
--cc=james@divide.org \
--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