From: Avi Kivity <avi@redhat.com>
To: "Ozan Çağlayan" <ozan@pardus.org.tr>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Poor KVM guest performance on an HP rack server
Date: Sat, 13 Mar 2010 10:21:08 +0200 [thread overview]
Message-ID: <4B9B4AF4.60306@redhat.com> (raw)
In-Reply-To: <4B9A775D.5070303@pardus.org.tr>
On 03/12/2010 07:18 PM, Ozan Çağlayan wrote:
> Jeremy Fitzhardinge wrote:
>
>> On 12/13/09 02:12, Ozan Çağlayan wrote:
>>
>>> Hmm, that's because we're using/developing a Linux distribution which
>>> doesn't have 64-bit support yet. But since the guest will be a
>>> compile-farm for our needs, it's worth trying to run an 64-bit distro on
>>> the host to see the difference, thanks for the tip but how much should
>>> this affect the performance?
>>>
>> 32-bit PAE is marginal above 4G of memory and the limit is at about 8G.
>> Above that, so much lowmem (<~1GB) is occupied by page and other kernel
>> structures that there's barely any memory to do any real work. If this
>> is what's happening, you'd expect to see poor host performance, and slow
>> guest performance would be secondary to that.
>>
> Updates on the issue after 3 months:
> ------------------------------------
>
> The host is now running an x86_64 2.6.32.9 kernel with kvm-2.6.32.7 built as an external module.
> The guest is 32-bit 2.6.32.9.
>
You're running an old kvm on a new kernel. It's simpler and better to
run the kvm that came with 2.6.32.9.
> I've booted the guest with -smp 4 -m 4096
>
> and I'm seeing the same slowness that I've mentioned in this thread during CUPS configuration.
> I'll try to send kvm_stat output in this week and try the same configure on another guest OS to see if it differs or not.
>
> I'm also thinking to build an optimized 2.6.33 for that rack server to see if things get better or not.
>
Better to find out what's wrong first and build kernels later.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2010-03-13 8:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-13 0:54 Poor KVM guest performance on an HP rack server Ozan Çağlayan
2009-12-13 6:10 ` Jeremy Fitzhardinge
2009-12-13 10:12 ` Ozan Çağlayan
2009-12-13 18:29 ` Jeremy Fitzhardinge
2010-03-12 17:18 ` Ozan Çağlayan
2010-03-13 8:21 ` Avi Kivity [this message]
2009-12-13 10:13 ` Avi Kivity
2009-12-13 11:36 ` Ozan Çağlayan
2009-12-13 11:58 ` Ozan Çağlayan
2009-12-15 10:29 ` Avi Kivity
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=4B9B4AF4.60306@redhat.com \
--to=avi@redhat.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ozan@pardus.org.tr \
/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