From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Ozan Çağlayan" <ozan@pardus.org.tr>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Poor KVM guest performance on an HP rack server
Date: Sat, 12 Dec 2009 22:10:50 -0800 [thread overview]
Message-ID: <4B24856A.4020507@goop.org> (raw)
In-Reply-To: <4B243B2B.806@pardus.org.tr>
On 12/12/09 16:54, Ozan Çağlayan wrote:
> We have an HP Proliant DL580G5 rack server. It has 4 Intel Xeon X7460(6
> core, 2.67GHz, 16MB L3) processor with 32GB of memory. /proc/cpuinfo has
> 24 x the following entry:
>
>
>
> I'm running 2.6.30.9-pae on top of it. We were actually planning to use
> it for a virtualization server for giving people dedicated *guest*
> access for their personal compile-farm needs.
>
Why are you running a 32-bit kernel on this machine? Sounds like a bad
mismatch.
J
next prev parent reply other threads:[~2009-12-13 6:10 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 [this message]
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
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=4B24856A.4020507@goop.org \
--to=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