Hi Eric,
Your overall issue is most likely resources - and you need to trace the VM
allocation through the logs and see how the calculations and where it falls
over as Andrija said - you will probably also see it putting the hosts in the
avoid list as it finds them to be unsuitable. Also keep in mind for good or bad
the error message "lack of resources" is sometimes a bit misleading - it's
sometimes used out of context.
Your core count hack sort of proves your point - by faking the number of cores
you effectively end up with double the amount of GHz in your cluster - at which
point CloudStack thinks you have enough resources. The failure is not a hard
limited core count in itself, it's down to the total amount of clock cycles x
OP factor compared to the disable threshold.
Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue
On 20/11/2018, 00:39, "Yiping Zhang" <yzh...@marketo.com> wrote:
Eric:
If you change any of memory or cpu over provisioning factors, you need to
restart (from GUI or API) all running VM instances, otherwise the reported
allocation/available numbers would still reflect data before your changes. If
you also add/delete instances at the same time, you could lose track of actual
allocated and available resources very quickly until you restart all your
instances.
Yiping
On 11/19/18, 3:59 PM, "Eric Lee Green" <eric.lee.gr...@gmail.com> wrote:
On 11/19/18 3:47 PM, Yiping Zhang wrote:
> Eric:
>
> What's your value for global setting cpu.overprovisioning.factor?
>
> I have this value set to 3.0. Right now, one of my servers with 32
cores @ 2.0 GHz (with HT enabled), I can allocate a total of 79 vCPU and 139
GHz to 26 VM instances. That's over 200% over provisioning!
I changed it to 4.0 and restarted the management server first thing. It
started out at 1.5. At 1.5, my zone shows 41% usage with the typical
workload -- 169.60Ghz / 409.78Ghz. I have 2x24x3.03ghz and
1x24x2.40ghz
servers for a total of 203.04Ghz actual, so even without the multiplier
I'm not over provisioning my CPU Mhz.
> On 11/19/18, 6:43 AM, "Andrija Panic" <andrija.pa...@gmail.com> wrote:
>
> Unless someone gives you better answer, I guess it's for fun -
to have more
> detailed numbers in dashboard (may be it's related to other
hypervisor
> types, just assuming... or not...)
>
> Cheers
>
>
dag.sonst...@shapeblue.com
www.shapeblue.com
Amadeus House, Floral Street, London WC2E 9DPUK
@shapeblue
On Mon, 19 Nov 2018 at 14:11, Ugo Vasi <ugo.v...@procne.it> wrote:
>
> > Hi Andrija,
> > not having noticed this new voice before I wondered if it is
limiting
> > the fact of reaching or exceeding the number of physical cores.
> >
> > What is the purpose of this dashboard pane?
> >
> >
> > Il 19/11/18 12:56, Andrija Panic ha scritto:
> > > Hi Ugo,
> > >
> > > Why would you want to do this, just curious ?
> > >
> > > I believe it's not possible, but anyway (at least with KVM,
probably same
> > > for other hypervisors) it doesn't even makes sense/use,
since when
> > > deploying a VM, ACS query host free/unused number of MHz
(GHz), so it's
> > not
> > > even relevant for ACS - number of cores in not relevant in
ACS
> > calculations
> > > during VM deployment.
> > >
> > >
> > > Cheers,
> > > Andrija
> > >
> > > On Mon, Nov 19, 2018, 11:31 Ugo Vasi
<ugo.v...@procne.it.invalid wrote:
> > >
> > >> Hi all,
> > >> in the dashboard of an ACS installation vesion 4.11.1.0
(Ubuntu 16.04
> > >> with KVM hypervisor), the new entry "# of CPU Cores"
appears.
> > >> Is it possible to over-provision like for MHz or storage?
> > >>
> > >> Thanks
> > >>
> > >>
> > >> --
> > >>
> > >> *Ugo Vasi* / System Administrator
> > >> ugo.v...@procne.it <mailto:ugo.v...@procne.it>
> > >>
> > >>
> > >>
> > >>
> > >> *Procne S.r.l.*
> > >> +39 0432 486 523
> > >> via Cotonificio, 45
> > >> 33010 Tavagnacco (UD)
> > >> www.procne.it <http://www.procne.it/>
> > >>
> > >>
> > >> Le informazioni contenute nella presente comunicazione ed i
relativi
> > >> allegati possono essere riservate e sono, comunque,
destinate
> > >> esclusivamente alle persone od alla Società sopraindicati.
La
> > >> diffusione, distribuzione e/o copiatura del documento
trasmesso da parte
> > >> di qualsiasi soggetto diverso dal destinatario è proibita
sia ai sensi
> > >> dell'art. 616 c.p., che ai sensi del Decreto Legislativo n.
196/2003
> > >> "Codice in materia di protezione dei dati personali". Se
avete ricevuto
> > >> questo messaggio per errore, vi preghiamo di distruggerlo e
di informare
> > >> immediatamente Procne S.r.l. scrivendo all' indirizzo e-mail
> > >> i...@procne.it <mailto:i...@procne.it>.
> > >>
> > >>
> > >
> > >
> > >
> >
> >
> > --
> >
> > *Ugo Vasi* / System Administrator
> > ugo.v...@procne.it <mailto:ugo.v...@procne.it>
> >
> >
> >
> >
> > *Procne S.r.l.*
> > +39 0432 486 523
> > via Cotonificio, 45
> > 33010 Tavagnacco (UD)
> > www.procne.it <http://www.procne.it/>
> >
> >
> > Le informazioni contenute nella presente comunicazione ed i
relativi
> > allegati possono essere riservate e sono, comunque, destinate
> > esclusivamente alle persone od alla Società sopraindicati. La
> > diffusione, distribuzione e/o copiatura del documento
trasmesso da parte
> > di qualsiasi soggetto diverso dal destinatario è proibita sia
ai sensi
> > dell'art. 616 c.p., che ai sensi del Decreto Legislativo n.
196/2003
> > "Codice in materia di protezione dei dati personali". Se avete
ricevuto
> > questo messaggio per errore, vi preghiamo di distruggerlo e di
informare
> > immediatamente Procne S.r.l. scrivendo all' indirizzo e-mail
> > i...@procne.it <mailto:i...@procne.it>.
> >
> >
>
> --
>
> Andrija Panić
>
>
