All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Schmitt <mas@scsy.de>
To: kvm@vger.kernel.org
Subject: Soft lockups and cpu frequency scaling
Date: Tue, 22 Dec 2009 14:16:49 +0100	[thread overview]
Message-ID: <4B30C6C1.9080508@scsy.de> (raw)

All,

I'm running a manually compiled KVM on CentOS 5.4. The KVM installation
has been carried over from CentOS 5.3, when KVM wasn't distributed with
the OS. (I tried to migrate to CentOS 5.4 native KVM support, but wasn't
able to get along with RedHat's interpretation of KVM.)

The KVM version used is 88, on Kernel 2.6.18-128.7.1.el5, as KVM doesn't
seem to compile on CentOS' current 2.6.18-164.9.1.el5.

Only on CentOS guests, I see very frequent "soft lockup" messages and
excessively hanging KVM instances. Long-term stability is fine (several
months uptime), but disturbed by the hangs. The problem already was
there on CentOS 5.3 as well. With the Debian guests on the same host, I
have never had any apparent problems.

A number of google results suggest that I should work with CPU scaling
on the CentOS guest systems, but unfortunately, CPU scaling is not
available in my guests. So, here's my question: How do I enable CPU
scaling in KVM guests? Or is there any other measure against these soft
lockups that you can recommend?

Thanks everyone,

-martin

-- 
Martin Schmitt / Schmitt Systemberatung / www.scsy.de
--> http://www.pug.org/index.php/Benutzer:Martin <--

             reply	other threads:[~2009-12-22 13:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-22 13:16 Martin Schmitt [this message]
2009-12-24 15:52 ` Soft lockups and cpu frequency scaling Marcelo Tosatti
2010-01-04 14:01   ` Martin Schmitt
2010-01-06  8:35     ` Marcelo Tosatti
2010-01-06  8:15       ` Martin Schmitt
2010-01-06  9:33         ` Marcelo Tosatti
2010-01-06  9:40           ` Martin Schmitt

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=4B30C6C1.9080508@scsy.de \
    --to=mas@scsy.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.