kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: dbareiro@gmx.net, KVM General <kvm@vger.kernel.org>
Subject: Re: Very high memory usage with KVM
Date: Sun, 26 Jul 2009 18:11:27 +0300	[thread overview]
Message-ID: <4A6C721F.8030702@redhat.com> (raw)
In-Reply-To: <20090726145603.GD31411@defiant.freesoftware.org>

On 07/26/2009 05:56 PM, Daniel Bareiro wrote:
>
>> What is the storage configuration? Are you using qcow2?
>>      
>
> I'm not using qcow2 files. The /dev/cciss/c0d0p3 partition is a physical
> volume that maintains the logical volumes that are used for VM's disks:
>
>    

In this case there should be no excessive memory usage.  qcow2 could use 
extra memory, especially on older qemu-kvm versions (or images created 
with older qemu-img versions).

>> What is the host kernel (uname -a)?
>>      
>
> root@ss02:~# uname -a
> Linux ss02 2.6.24-19-server #1 SMP Wed Aug 20 18:43:06 UTC 2008 x86_64 GNU/Linux
>
>    

kvm memory management with pre 2.6.27 host kernels is pretty weak.  
Using a newer host kernel (and newer kvm) may solve this problem.

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


  reply	other threads:[~2009-07-26 15:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-25 17:43 Very high memory usage with KVM Daniel Bareiro
2009-07-26 11:31 ` Avi Kivity
2009-07-26 14:56   ` Daniel Bareiro
2009-07-26 15:11     ` Avi Kivity [this message]
2009-07-26 15:50       ` Daniel Bareiro
2009-07-26 16:19         ` Avi Kivity
2009-08-08  0:54           ` Daniel Bareiro
2009-08-09  9:12             ` Avi Kivity
2009-08-10  6:40             ` Bernhard Held
2009-08-10 15:22               ` Daniel Bareiro
2009-08-10 16:15                 ` Bernhard Held
2009-08-22  2:28                   ` Daniel Bareiro

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=4A6C721F.8030702@redhat.com \
    --to=avi@redhat.com \
    --cc=dbareiro@gmx.net \
    --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;
as well as URLs for NNTP newsgroup(s).