From: Mark McLoughlin <markmc@redhat.com>
To: Max Kellermann <max@duempel.org>
Cc: Jan Niehusmann <jan@gondor.com>, kvm@vger.kernel.org
Subject: Re: KVM guest lockup
Date: Mon, 12 Jan 2009 17:09:20 +0000 [thread overview]
Message-ID: <1231780160.4290.164.camel@localhost.localdomain> (raw)
In-Reply-To: <20081222105738.GA27409@squirrel.roonstrasse.net>
On Mon, 2008-12-22 at 11:57 +0100, Max Kellermann wrote:
> On 2008/12/21 12:55, Jan Niehusmann <jan@gondor.com> wrote:
> > As I observed such behaviour only when the host has frequency
> > scaling activated: Could it be that in this case,
> > clocksource_read(clock) on the guest is misbehaving?
>
> Indeed, the host had governor=ondemand. After the switch to
> "performance", the guest seems to run stable.
>
> So this is a bug in the guest kernel, by making wrong assumptions on
> the clock values retrieved from the host, right?
FWIW, several Fedora users are also seeing guest lockups with kvm-clock
in the guest and frequency scaling enabled in the host. See:
https://bugzilla.redhat.com/475598
Cheers,
Mark.
prev parent reply other threads:[~2009-01-12 17:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-19 17:44 KVM guest lockup Max Kellermann
2008-12-20 12:15 ` Jan Niehusmann
2008-12-21 11:55 ` Jan Niehusmann
2008-12-22 10:57 ` Max Kellermann
2009-01-12 17:09 ` Mark McLoughlin [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=1231780160.4290.164.camel@localhost.localdomain \
--to=markmc@redhat.com \
--cc=jan@gondor.com \
--cc=kvm@vger.kernel.org \
--cc=max@duempel.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.