Assuming you are on KVM...total number of Shares = total number of Mhz
(cores * Mhz) / cpuOverprovisioningFactor - cpu shares get changed (after
changing cpu overprovisioning) only when you stop and start an existing VM.
So i.e. 2 vCPU of 2000 MHz VM, with CPU overprovisioning of 2 will get
(2
Hello,
How VMs receive CPU shares when cpu over provisioning factor is increased
and CPU cap is disabled for them?
Thanks
No (currently).
Perhaps in next year or so, we *might* have some changes around that, but
atm - no.
Andrija
On Wed, 26 Jun 2019 at 14:52, Fariborz Navidan
wrote:
> Hello All,
>
> Is there any way to force ACS to take into consideration the new cpu
> overprovision factor without having to shoutd
Hello All,
Is there any way to force ACS to take into consideration the new cpu
overprovision factor without having to shoutdown lots of VMs on the host?
Thanks
t;
>> Swen Brüseke
>>
>> -Ursprüngliche Nachricht-
>> Von: Abhinandan Prateek [mailto:abhinandan.prat...@shapeblue.com]
>> Gesendet: Mittwoch, 22. April 2015 06:35
>> An: users@cloudstack.apache.org
>> Betreff: Re: cpu overprovisioning
>>
>> Ca
-Ursprüngliche Nachricht-
Von: Abhinandan Prateek [mailto:abhinandan.prat...@shapeblue.com]
Gesendet: Mittwoch, 22. April 2015 06:35
An: users@cloudstack.apache.org
Betreff: Re: cpu overprovisioning
Can we fix the dashboard to reflect the available capacity given an over commit
?
On 22
Nachricht-
Von: Abhinandan Prateek [mailto:abhinandan.prat...@shapeblue.com]
Gesendet: Mittwoch, 22. April 2015 06:35
An: users@cloudstack.apache.org
Betreff: Re: cpu overprovisioning
Can we fix the dashboard to reflect the available capacity given an over commit
?
> On 22-Apr-2015, at 9:56
rüseke - proIO GmbH <
>> s.brues...@proio.com<mailto:s.brues...@proio.com>> wrote:
>>
>> Please try to stop and start the vm. Maybe reboot is not working here. You
>> should start to see more free CPU after the first vm.
>>
>> Mit freundlichen Grüßen / W
eke
>
> -Ursprüngliche Nachricht-
> Von: Ugo Vasi [mailto:ugo.v...@procne.it]
> Gesendet: Dienstag, 21. April 2015 16:40
> An: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org>
> Betreff: Re: AW: cpu overprovisioning
>
> Hi Swen,
> I try rebboting 2
reundlichen Grüßen / With kind regards,
Swen Brüseke
-Ursprüngliche Nachricht-
Von: Ugo Vasi [mailto:ugo.v...@procne.it]
Gesendet: Dienstag, 21. April 2015 16:40
An: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org>
Betreff: Re: AW: cpu overprovisioning
Hi Swen,
I tr
ag, 21. April 2015 16:40
> An: users@cloudstack.apache.org
> Betreff: Re: AW: cpu overprovisioning
>
> Hi Swen,
> I try rebboting 2 vm but the amount of cpu MHz is not changed. Do I have
> to restart all vm before you see a change?
>
>
> Il 21/04/2015 16:16, S. Brü
2015 16:40
An: users@cloudstack.apache.org
Betreff: Re: AW: cpu overprovisioning
Hi Swen,
I try rebboting 2 vm but the amount of cpu MHz is not changed. Do I have to
restart all vm before you see a change?
Il 21/04/2015 16:16, S. Brüseke - proIO GmbH ha scritto:
> This is because the factor
By instance I mean VM.
Mit freundlichen Grüßen / With kind regards,
Swen Brüseke
-Ursprüngliche Nachricht-
Von: Rafael Weingartner [mailto:rafaelweingart...@gmail.com]
Gesendet: Dienstag, 21. April 2015 16:28
An: users@cloudstack.apache.org
Betreff: Re: cpu overprovisioning
When you
[mailto:ugo.v...@procne.it]
Gesendet: Dienstag, 21. April 2015 16:06
An: users@cloudstack.apache.org
Betreff: Re: cpu overprovisioning
If I change the over-provisioning ratio in cluster-relative settings
(infrastructure->cluser->cluster-name->settings) the dashboard show the sum of
rea
t-
> Von: Ugo Vasi [mailto:ugo.v...@procne.it]
> Gesendet: Dienstag, 21. April 2015 16:06
> An: users@cloudstack.apache.org
> Betreff: Re: cpu overprovisioning
>
> If I change the over-provisioning ratio in cluster-relative settings
> (infrastructure->cluser->cluster-name->sett
freundlichen Grüßen / With kind regards,
Swen Brüseke
-Ursprüngliche Nachricht-
Von: Ugo Vasi [mailto:ugo.v...@procne.it]
Gesendet: Dienstag, 21. April 2015 16:06
An: users@cloudstack.apache.org
Betreff: Re: cpu overprovisioning
If I change the over-provisioning ratio in cluster-relative
If I change the over-provisioning ratio in cluster-relative settings
(infrastructure->cluser->cluster-name->settings) the dashboard show the
sum of real GHz the overprovisioned amount of GHz (324GHz) as aspected,
but after a while also the sum of Ghz is multiplied by the same factor
making it u
In case of cloudstack, cpu capacity for host is total of cpus * no of Ghz *
overporvisoning.
total capacity = sum of capacities of individual hosts.
Thanks,
Bharat.
On 21-Apr-2015, at 6:49 pm, Abhinandan Prateek
wrote:
> Available CPU will be 3 times the actual CPU when over provisioned by
Available CPU will be 3 times the actual CPU when over provisioned by 3.
The UI not showing the over provisioned value seems like a bug.
-abhi
> On 21-Apr-2015, at 6:34 pm, Ugo Vasi wrote:
>
> Hi all,
> we have a cluster of three machines with 16 CPU at 2.2GHz each and we have
> set a cpu-ove
Hi all,
we have a cluster of three machines with 16 CPU at 2.2GHz each and we
have set a cpu-overprovizioning to 3.
I would expect that the CPU system capacity of the dashboard appear with
the sum of megahertz CPUs multiplied by three instead I get the real sum
(108MHz).
I do not understand
freundlichen Grüßen / With kind regards,
Swen Brüseke
-Ursprüngliche Nachricht-
Von: ilya [mailto:ilya.mailing.li...@gmail.com]
Gesendet: Samstag, 18. April 2015 02:27
An: users@cloudstack.apache.org
Betreff: Re: KVM CPU Overprovisioning issues.
When the deployment goes through, the allocation
the VM and
note the job id (i see in your log it was job-7312) in
management-server.log . Once you have the job id, grep 'job-'
management-server.log. Post the content here... I do see you post it the
log below, it appears we are missing some info.
You can override CPU overpr
Sure enough.
Its been a while since I configured a new cluster, I completely forgot
they had their own over-provisioning limits.
Thanks!
On Fri, Apr 17, 2015 at 4:10 PM, Andrija Panic wrote:
> If not mistaken, there is global overprovisioning factor, and there is
> cluster level overprovisionin
If not mistaken, there is global overprovisioning factor, and there is
cluster level overprovisioning - the last one takes presedence I think...
On 17 April 2015 at 23:01, Grayson Head wrote:
> I'm trying to figure out how CPU over-provisioning works in
> cloudstack. It seems that no matter how
I'm trying to figure out how CPU over-provisioning works in
cloudstack. It seems that no matter how much I change the
over-provisioning factor value in global settings, I cannot
over-provision CPU allocation on the hosts. I suspect that I'm just
having a lack of understanding on my part, but it see
it is over provisioned.
> 4-From the kvm Point of view : I guess you are interested in Cloudstack
> point of view so leaving it
>
> Thanks
> Prashant
>
> -Original Message-
> From: Ivan Rodriguez [mailto:ivan...@gmail.com]
> Sent: Tuesday, June 17, 2014 11:55
Message-
From: Ivan Rodriguez [mailto:ivan...@gmail.com]
Sent: Tuesday, June 17, 2014 11:55 AM
To: cloudstack-us...@incubator.apache.org
Subject: Re: Cloudstack 4.3 KVM CPU overprovisioning
More information from my previous post,
On this particular blade I only have 9 vm's running
Total CP
More information from my previous post,
On this particular blade I only have 9 vm's running
Total CPU24 x 2.79 GHzCPU Utilized3.9%CPU Allocated for VMs 97%Memory
Total126.02
GBMemory Allocated53.50 GB Memory Used36.74 MBNetwork Read35.99 GBNetwork
Write
[root@cs2-chas1-bl03 ~]# virsh list
Id
Dear Cloudstack users,
Our current setup is using dell blades with 24 cpus on KVM,
currently we have 5 servers like that(120 cpus) , and 28 Vm's currently
running all of them linux centos
with virtio modules the majority of the vm's have 2 vcpus per VM
so that would be around 56 vcpus
According
Super !!! Fixed. Thanks for heads-up.
> That is what i didn't know about. Is it possible to update that
> settings for existing cluster ?
>> Did you change the global setting or the cluster setting ?
>> In 4.2 changing global setting only affects the newly created clusters
>> factor not the exi
That is what i didn't know about. Is it possible to update that settings for
existing cluster ?
> Did you change the global setting or the cluster setting ?
> In 4.2 changing global setting only affects the newly created clusters
> factor not the existing ones.
>
> On 27/11/13 12:26 PM, "d...@so
Did you change the global setting or the cluster setting ?
In 4.2 changing global setting only affects the newly created clusters
factor not the existing ones.
On 27/11/13 12:26 PM, "d...@soleks.com" wrote:
>
>
>Hi all,
>
>I configured CPU over provisioning factor 2.0 but cloudstack (4.2) show
Did you restart the management service after making the change?
Regards,
Kirk Jantzer
http://about.me/kirkjantzer
On Wed, Nov 27, 2013 at 3:26 PM, wrote:
>
>
> Hi all,
>
> I configured CPU over provisioning factor 2.0 but cloudstack (4.2) shows
> no changes on the dashboard. computational no
Hi all,
I configured CPU over provisioning factor 2.0 but cloudstack (4.2) shows no
changes on the dashboard. computational nodes are XenServer 6.2, 2x4cores. Any
hints are more then welcome.
Dan.
This message was sent using
34 matches
Mail list logo