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
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
small tip - if you change cpu overprovisioning on CLUSTER level, no need to
restart management server - it's applied immediately on the fly.
On Tue, 20 Nov 2018 at 00:59, Eric Lee Green
wrote:
> On 11/19/18 3:47 PM, Yiping Zhang wrote:
> > Eric:
> >
> > What's your value for global setting
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
FYI, tested again (CPU overprovisioning factor=1 on both Cluster and Global
level - so NO overprovisioning)
deployed VM unti it failed (could not deploy any more):
At moment of failure:
cpu used 79% (90% is disabled threshold, but VMs is big one, so would cause
91-92% usage)
number of cpu cores:
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!
Yiping
On
t from the VMware allocator?
>
> From: Dag Sonstebo
> Sent: Monday, November 19, 2018 9:47 AM
> To: users@cloudstack.apache.org
> Subject: Re: number of cores
>
> Andrija - not sure about your 3.4GHz cores - must a be a simplified lookup
> somewhere making assumptions.
>
@cloudstack.apache.org
Subject: Re: number of cores
Andrija - not sure about your 3.4GHz cores - must a be a simplified lookup
somewhere making assumptions.
Eric - have just tried your scenario in my 4.11.2RC5 lab (admittedly with
VMware, not KVM) - and I can see my core allocation keeps going up
https://pasteboard.co/HNVkBpv.png
All fine, but note that my CPU GHZ is NOT over 80% (I believe 0.8 aka 80%
is the cpu warning or disable threshold)
As Dag said, please check from mgmt logs why you can't actually spin new VM
in your case.
When you start to deploy VM, there will be some friendly
Let me test this also, on clean 4.11.2 RC5... (KVM)
On Mon, 19 Nov 2018 at 18:47, Dag Sonstebo
wrote:
> Andrija - not sure about your 3.4GHz cores - must a be a simplified lookup
> somewhere making assumptions.
>
> Eric - have just tried your scenario in my 4.11.2RC5 lab (admittedly with
>
Andrija - not sure about your 3.4GHz cores - must a be a simplified lookup
somewhere making assumptions.
Eric - have just tried your scenario in my 4.11.2RC5 lab (admittedly with
VMware, not KVM) - and I can see my core allocation keeps going up, e.g. at the
moment it sits at 166% - 10 out of
On 11/19/18 03:56, Andrija Panic wrote:
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
Thx Dag for confirmation.
Speaking about CPU cores - I do have one "problem" which not sure is
possible to solve in meaningful way
2 x 8 core Intel Xeon E5 2.6GHz nominally (with HT enabled), with burst to
3.4 GHz ( but ! only a few cores can burst to that 3.4 - not all at the
same time !) -
Ultimately there will always be a 1-to-1 relationship between vCPU cores and
physical cores - you can't make a 4vCPU VM run on an "overprovisioned 2
physical core" hypervisor (unless you consider Intel HT to be exactly this).
You can only overprovision time slices of your total clock cycles. If
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
On Mon, 19 Nov 2018 at 14:11, Ugo Vasi wrote:
> Hi Andrija,
> not having noticed this new voice before I
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 ?
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 -
17 matches
Mail list logo
