From: Martin Maurer <martin@proxmox.com>
To: Alexey Eremenko <al4321@gmail.com>
Cc: kvm-devel@lists.sourceforge.net
Subject: Re: can KVM use all cpu cores in a guest
Date: Fri, 14 Mar 2008 15:28:12 +0100 [thread overview]
Message-ID: <47DA8B7C.8090206@proxmox.com> (raw)
In-Reply-To: <7fac565a0803070831i1748019fte1eabe3a55384d60@mail.gmail.com>
Alexey Eremenko wrote:
> KVM fully uses all 4 CPUs.
>
> 1. You need to make sure KVM is activated (not Qemu).
> 2. You need to have the guest workload to be multi-threaded.
>
>
Hi Alexey,
Thanks, I worked it out - I had an issue on the kernel and on my custom
resource scheduling, now it is working with kernel 2.6.24 and the guest
can use all 4 cpu´s. best regards,
martin
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
prev parent reply other threads:[~2008-03-14 14:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-07 14:24 can KVM use all cpu cores in a guest Martin Maurer
2008-03-07 16:31 ` Alexey Eremenko
2008-03-14 14:28 ` Martin Maurer [this message]
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=47DA8B7C.8090206@proxmox.com \
--to=martin@proxmox.com \
--cc=al4321@gmail.com \
--cc=kvm-devel@lists.sourceforge.net \
/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.