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 19:19:39 +0300 [thread overview]
Message-ID: <4A6C821B.5020007@redhat.com> (raw)
In-Reply-To: <20090726155012.GE31411@defiant.freesoftware.org>
On 07/26/2009 06:50 PM, Daniel Bareiro wrote:
>> 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.
>>
>
> Initially I am going to see how it improves the situation upgrading to
> KVM-84 of backports of Hardy Heron, since at the moment last kernel
> available for Hardy is the one I has commented.
>
> I would like to know if the newest versions of KVM published in the
> official site of the project solve a bug recently reported in Ubuntu
> Launchpad [1]. Also I was observing errors of type 'to swapper Not
> tainted' or 'java Not tainted' in the VM (aps2, with a high rate of I/O)
> and that I've commented in a previous message sent to the list [2]. I
> would want to know if you could indicate to me if this can be due to KVM
> bug that would be solved in a later version.
>
>
My guess is that it is due to poor swapping with pre-2.6.27 hosts. 15 GB
used out of 16GB total is just 6% reserve, which may be a bit too low.
With a 2.6.27 host some small amount of memory would be swapped out,
before that you'd see thrashing. Another way to check is to drop one
guest (or reduce total memory needed by 1GB) and see if you get the same
results or if things improve.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-07-26 16:15 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
2009-07-26 15:50 ` Daniel Bareiro
2009-07-26 16:19 ` Avi Kivity [this message]
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=4A6C821B.5020007@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).