[one-users] CPU and Memory Overcommitment

[Carlos Martín Sánchez]

Hi,

On Tue, Sep 3, 2013 at 1:32 PM, Igor Laskovy <igor.laskovy at gmail.com> wrote:

> Hello all!
>
> I found that this already have discussed not so far from now -
> http://comments.gmane.org/gmane.comp.distributed.opennebula.user/10568
>
> As understand for now about Memory over-commitment for production I can
> forget ;)
>
> For CPU over-commitment I can only use CPU & VCPU attributes, right?
>

That's right


> If I will, for example, set CPU to 0.2, than host will do only reservation
> of processor time for that VM OR do limit ether, so this VM will limited of
> 1/5 of one physical/logical hardware core?
>

We enforce the CPU reserved at hypervisor level with cgroups for kvm,
credit scheduler for xen, and the esx cpu scheduler for vmware

Regards

--
Join us at OpenNebulaConf2013 <http://opennebulaconf.com/> in Berlin, 24-26
September, 2013
--
Carlos Martín, MSc
Project Engineer
OpenNebula - The Open-source Solution for Data Center Virtualization
www.OpenNebula.org <http://www.opennebula.org/> | cmartin at opennebula.org |
@OpenNebula <http://twitter.com/opennebula>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20130904/bc26109c/attachment-0002.htm>