From: Thomas Fjellstrom <tfjellstrom@shaw.ca>
To: kvm@vger.kernel.org
Subject: Re: Reserve CPU cores for specific guests?
Date: Sun, 8 Nov 2009 20:14:05 -0700 [thread overview]
Message-ID: <200911082014.05845.tfjellstrom@shaw.ca> (raw)
In-Reply-To: <64B8A9B90F804CDF998387C037871E50@neilhp>
On Sun November 8 2009, Neil Aggarwal wrote:
> > I think you can achieve that on some simple level DIY with
> > taskset from
> > util-linux(-ng).
>
> That is a good utility to know. I did not know about that
> earlier. Thanks for the info.
>
> I am wondering one thing though:
>
> I will either need to call taskset when executing the
> process or run taskset on a PID after it starts up.
>
> Unless there is a way to tell KVM to call taskset when starting
> a guest, I think that is going to be hard to automate since the
> guests will get different PID each time they are started.
>
> Any suggestions?
>
None directly related, but libvirt's kvm support supports pinning a vm to a
physical cpu. At least it has the option in virt-manager.
> Thanks,
> Neil
>
> --
> Neil Aggarwal, (281)846-8957, http://www.JAMMConsulting.com
> CentOS 5.4 KVM VPS $55/mo, no setup fee, no contract, dedicated 64bit CPU
> 1GB dedicated RAM, 40GB RAID storage, 500GB/mo premium BW, Zero downtime
>
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Thomas Fjellstrom
tfjellstrom@shaw.ca
next prev parent reply other threads:[~2009-11-09 3:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-08 22:56 Reserve CPU cores for specific guests? Neil Aggarwal
2009-11-09 0:26 ` Zdenek Kaspar
2009-11-09 3:12 ` Neil Aggarwal
2009-11-09 3:14 ` Thomas Fjellstrom [this message]
2009-11-09 5:08 ` Neil Aggarwal
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=200911082014.05845.tfjellstrom@shaw.ca \
--to=tfjellstrom@shaw.ca \
--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.