From: Alejandro Comisario <alejandro.comisario@mercadolibre.com>
To: kvm@vger.kernel.org
Subject: kvm cpu usage allocation
Date: Wed, 19 Feb 2014 18:42:56 -0300 [thread overview]
Message-ID: <CAMrG31zA6G-LyoxePODPZYHKmtWh1_U_eVyUR5_7xF+jO-c-sg@mail.gmail.com> (raw)
Hi everyone.
We are having a private cloud with more than 1000 phy servers.
Each server has 128GB of RAM and 24 cores (2 heaxacores with HT
enabled), but the amount of vms running on those servers versus the
flavor (amount of CPU) made us use about 80 VCPUS.
The questions are as follow.
* is there a fine documentation of HOW kvm handles cpu allocation/pin
per vm in an scenario like this one ?
* is there also, a documentation that explains under a circumstance
where a VM needs more processing power, how priority is managed ?
* is there a way to define some kind of politics or rules to have
specific cpu pinning for specific vms ?
So, well ... any extensive information to understand how KVM behaves
would be great!
Thanks as allways!
----------
@lejandrito
next reply other threads:[~2014-02-19 21:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 21:42 Alejandro Comisario [this message]
2014-02-20 14:31 ` kvm cpu usage allocation Alejandro Comisario
2014-02-20 23:00 ` Marcelo Tosatti
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=CAMrG31zA6G-LyoxePODPZYHKmtWh1_U_eVyUR5_7xF+jO-c-sg@mail.gmail.com \
--to=alejandro.comisario@mercadolibre.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.