From: Dor Laor <dor.laor@qumranet.com>
To: Yuksel Gunal <yuksel.gunal@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: Reserving CPU resources for a KVM guest
Date: Sun, 24 Aug 2008 00:58:43 +0300 [thread overview]
Message-ID: <48B08813.2000709@il.qumranet.com> (raw)
In-Reply-To: <00e001c90494$a459a8a0$6600a8c0@YukselsLaptop>
Yuksel Gunal wrote:
> Hi,
>
> I have been playing with KVM and was wondering about the following
> question: is there a resource configuration setting that would enforce
> a fraction of CPU to be guaranteed for a KVM guest? What I have on
> mind is something similar to the "reservation" setting on VMware (used
> to be called minimum CPU), which guarantees a number of CPU cycles to
> a VM. Also, any configuration setting similar to CPU/Memory Shares
> setting in VMware, which will kick in under contention for resources?
>
VM is like any other process in Linux, you can use cpu controller,
cgroups or any other scheduling option for your VMs.
prev parent reply other threads:[~2008-08-23 21:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-22 20:21 Reserving CPU resources for a KVM guest Yuksel Gunal
2008-08-23 21:58 ` Dor Laor [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=48B08813.2000709@il.qumranet.com \
--to=dor.laor@qumranet.com \
--cc=kvm@vger.kernel.org \
--cc=yuksel.gunal@gmail.com \
/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