From: "Ozan Çağlayan" <ozan@pardus.org.tr>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Poor KVM guest performance on an HP rack server
Date: Sun, 13 Dec 2009 12:12:39 +0200 [thread overview]
Message-ID: <4B24BE17.805@pardus.org.tr> (raw)
In-Reply-To: <4B24856A.4020507@goop.org>
Jeremy Fitzhardinge wrote:
>
> Why are you running a 32-bit kernel on this machine? Sounds like a
> bad mismatch.
>
> J
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?
Thanks.
next prev parent reply other threads:[~2009-12-13 10:12 UTC|newest]
Thread overview: 11+ 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 [this message]
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-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=4B24BE17.805@pardus.org.tr \
--to=ozan@pardus.org.tr \
--cc=jeremy@goop.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.