public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Harald Dunkel <harri@darkharri.de>
Cc: KVM Mailing List <kvm@vger.kernel.org>
Subject: Re: how to tweak kernel to get the best out of kvm?
Date: Mon, 08 Mar 2010 13:02:31 +0200	[thread overview]
Message-ID: <4B94D947.3060303@redhat.com> (raw)
In-Reply-To: <4B912156.5020707@darkharri.de>

On 03/05/2010 05:20 PM, Harald Dunkel wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi folks,
>
> Problem: My kvm server (8 cores, 64 GByte RAM, amd64) can eat up
> all block device or file system performance, so that the kvm clients
> become almost unresponsive. This is _very_ bad. I would like to make
> sure that the kvm clients do not affect each other, and that all
> (including the server itself) get a fair part of computing power and
> memory space.
>    

Please describe the issue in detail, provide output from 'vmstat' and 'top'.

> What config options would you suggest to build and run a Linux
> kernel optimized for running kvm clients?
>
> Sorry for asking, but AFAICS some general guidelines for kvm are
> missing here. Of course I saw a lot of options in Documentation/\
> kernel-parameters.txt, but unfortunately I am not a kernel hacker.
>
> Any helpful comment would be highly appreciated.
>    

One way to ensure guests don't affect each other is not to overcommit, 
that is make sure each guest gets its own cores, there is enough memory 
for all guests, and guests have separate disks.  Of course that defeats 
the some of the reasons for virtualizing in the first place; but if you 
share resources, some compromises must be made.

If you do share resources, then Linux manages how they are shared.  The 
scheduler will share the processors, the memory management subsystem 
will share memory, and the I/O scheduler will share disk bandwidth.  If 
you see a problem in one of these areas you will need to tune the 
subsystem that is misbehaving.

There is also a larger effort to improve control of sharing called 
control groups (cgroups).  You may want to read up on this as it can 
provide very fine grain control on resource sharing.

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


  reply	other threads:[~2010-03-08 11:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-05 15:20 how to tweak kernel to get the best out of kvm? Harald Dunkel
2010-03-08 11:02 ` Avi Kivity [this message]
     [not found]   ` <4B979776.1000701@aixigo.de>
2010-03-10 13:15     ` Avi Kivity
2010-03-10 15:57       ` Javier Guerra Giraldez
2010-03-10 16:00         ` Avi Kivity
2010-03-11 13:24       ` Harald Dunkel
2010-03-13  8:54         ` Avi Kivity
2010-03-15 13:54           ` Harald Dunkel
  -- strict thread matches above, loose matches on Subject: below --
2010-04-23  8:47 Alec Istomin

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=4B94D947.3060303@redhat.com \
    --to=avi@redhat.com \
    --cc=harri@darkharri.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