public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Lennert Buytenhek <buytenh@wantstofly.org>
Cc: kvm@vger.kernel.org, lfarkas@lfarkas.org, davej@codemonkey.org.uk
Subject: Re: fedora 10 x86_64 breakage under KVM, due to KVM_CLOCK
Date: Mon, 20 Apr 2009 14:56:12 +0300	[thread overview]
Message-ID: <49EC62DC.5080900@redhat.com> (raw)
In-Reply-To: <20090420112613.GA1860@mail.wantstofly.org>

Lennert Buytenhek wrote:
> (please CC, not on the list)
>
> Hi all,
>
> Fedora 10 randomly hangs for me when run under KVM, whereas (unpatched)
> F9 works fine.  When this happens, kvm_stat shows that the VM is seeing
> 1000 IRQ exits per second, but nothing else seems to happen.  The latest
> F9 update kernel seems to be bust as well.  (I noticed that the KVM guest
> support status page says that "Alexey E." is seeing the same thing.)
>
> I tried about two dozen different kernel packages from koji, and it turns
> out that kernel-2.6.26-0.122.rc9.git4.fc10 is the last known good kernel,
> and kernel-2.6.26-0.124.rc9.git5.fc10 is the first kernel that's broken.
>
> The F10 instability appears since this commit (attached below as well):
>
> 	http://fedora.gitbits.net/?p=kernel;a=commit;h=a5991f36968f44d4d3c64fc5aaa285a21de1ba54
>
> I built three new kernels from the latest 2.6.27-170.2.56.fc10 update
> in Fedora 10:
> 1. One with PARAVIRT and all associated options disabled entirely.
> 2. One with only KVM_GUEST disabled.
> 3. One with only KVM_CLOCK disabled (and paravirt and KVM_GUEST enabled).
>
> Kernel (1) is stable.  Kernel (2) is unstable like the unpatched F10
> kernels are, in that it randomly locks up.  Kernel (3) is stable as
> well, which suggests that KVM_CLOCK is what's causing the lockups.
>
> I tried booting the original F10 update kernel with no-kvmclock on
> the command line as well, and that makes things stable as well.
>
> I tried with the latest F10 updates-testing kernel (2.6.29.1-30.fc10),
> and that shows the same thing: with no-kvmclock it works fine, otherwise
> it hangs randomly.
>
> Running KVM 84 on x86_64 CentOS 5.3, with the kvm rpms from lfarkas.org.
> The host CPU is a Q6600 Core 2 Quad.
>
> Any ideas?
>   

This is a known issue.  While kvm-84 fixed kvmclock, an issue remained 
with cpu frequency scaling on older host kernels (including RHEL 5 / 
CentOS 5).  kvm-85 (to be released shortly) contains a fix (b395d156477a 
in kvm-userspace.git).


-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2009-04-20 11:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-20 11:26 fedora 10 x86_64 breakage under KVM, due to KVM_CLOCK Lennert Buytenhek
2009-04-20 11:56 ` Avi Kivity [this message]
2009-04-25 21:30   ` Lennert Buytenhek

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=49EC62DC.5080900@redhat.com \
    --to=avi@redhat.com \
    --cc=buytenh@wantstofly.org \
    --cc=davej@codemonkey.org.uk \
    --cc=kvm@vger.kernel.org \
    --cc=lfarkas@lfarkas.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