Hi, CPU overcommit is a bit weird as the primary count that ACS does is on "Megahertz" rather than on vCPU. What I do in order to overcommit (and keep it simple) is just set the Mhz of the CPU the same number as the CPU/core count of the offering, this way it will take a very serious amount of instances to fill up a machine (ie the sum of all Mhz allocated to exceed total Mhz of the host as reported by libvirt).
HTH Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro ----- Original Message ----- From: "Harikrishna Patnala" <harikrishna.patn...@citrix.com> To: users@cloudstack.apache.org Sent: Tuesday, 17 June, 2014 2:03:53 PM Subject: Re: Cloudstack 4.3 KVM cpu overcommit Hi Ivan, Please take a look at “capacity calculations on MS” section in the following wiki for better understanding. https://cwiki.apache.org/confluence/display/CLOUDSTACK/CPU+and+RAM+Overcommit Thanks Harikrishna On 17-Jun-2014, at 5:52 pm, Ivan Rodriguez <ivan...@gmail.com> wrote: > The vm is not the problem but rather cloudstack finding that almost all my > CPU is being allocated > >> api listCapacity type=1 > count = 1 > capacity: > capacitytotal = 335112 > capacityused = 188000 > percentused = 56.1 > type = 1 > zoneid = 9e929a84-e93d-4233-9521-a93636c18bd9 > zonename = CS2-CHAS1-ZONE01 > > 56 % matches against the dashboard it seems that if I change the KVM Max > Guest limit to any number it won't change the percentage usage > > > > > > On Tue, Jun 17, 2014 at 10:18 PM, François Bousquet < > francois.bousq...@radialpoint.com> wrote: > >> By experience, you need to stop/start VM to see them use the over >> provisioning factor. >> >>> On Jun 17, 2014, at 8:02, "Ivan Rodriguez" <ivan...@gmail.com> wrote: >>> >>> Hi there, >>> >>> I can confirm that my KVM hypervisor is overcommiting CPU correctly, >>> but cloudstack seems unable to do so. >>> >>> How does cloudstack calculates the usage per host ? >>> >>> Cheers >> *********************************************************************** >> This e-mail and attachments are confidential, legally privileged, may be >> subject to copyright and sent solely for the attention of the addressee(s). >> Any unauthorized use or disclosure is prohibited. Statements and opinions >> expressed in this e-mail may not represent those of Radialpoint. >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Le contenu du présent >> courriel est confidentiel, privilégié et peut être soumis à des droits >> d'auteur. Il est envoyé à l'intention exclusive de son ou de ses >> destinataires. Il est interdit de l'utiliser ou de le divulguer sans >> autorisation. Les opinions exprimées dans le présent courriel peuvent >> diverger de celles de Radialpoint. >>
