From: Avi Kivity <avi@redhat.com>
To: Drew Johnson <drewtomjohnson@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: Guest virtual CPUs limited to only 50% of host CPU
Date: Tue, 05 Apr 2011 12:03:39 +0300 [thread overview]
Message-ID: <4D9ADAEB.1030301@redhat.com> (raw)
In-Reply-To: <AANLkTikMRv-agWtNHsUt9jEBssRr4mMO-pP_Uo4KT1YS@mail.gmail.com>
On 03/31/2011 11:03 PM, Drew Johnson wrote:
> Hi,
>
> I am using Qemu-KVM-0.12.5
This is somewhat old. Try upgrading.
> on Intel Xeon (Vt-x enabled) processors and
> monitoring the system using htop on the host. On the processors that
> are running Qemu-KVM I am seeing a 50/50 split between userspace and
> guest ("gu:" in htop). I have pinned the vCPU qemu-kvm threads to
> specific host CPUs using taskset. In the guest the CPUs are nearly
> 100% userspace in htop.
>
> Does anyone have ideas on why this is? Is there a way I can get much
> higher utilization for the guest virtual CPUs wrt the host?
>
Please build qemu with --disable-cpu-strip and run 'perf top' to see
what's going on.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-04-05 9:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 21:03 Guest virtual CPUs limited to only 50% of host CPU Drew Johnson
2011-04-05 9:03 ` Avi Kivity [this message]
2011-04-29 0:30 ` Drew Johnson
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=4D9ADAEB.1030301@redhat.com \
--to=avi@redhat.com \
--cc=drewtomjohnson@gmail.com \
--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 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.