You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by li jerry <di...@hotmail.com> on 2019/07/19 14:53:54 UTC
答复: The role of CPU (in MHz) in Compute Offerings
Thank you, Andrija.
发件人: Andrija Panic<ma...@gmail.com>
发送时间: 2019年7月19日 16:14
收件人: users<ma...@cloudstack.apache.org>
主题: Re: The role of CPU (in MHz) in Compute Offerings
The difference is:
VMware - no difference, unless you set "CPU cap" on the Compute Offering -
than the limit will be set to the number of MHz per the offering
XenServer - no difference, unless you set "CPU cap" on the Compute Offering
- similar to VMware
KVM - no difference no matter if "CPU cap" before 4.11, but in 4.11 it's
there if "CPU cap" is set on the Compute Offering
https://github.com/apache/cloudstack/pull/2482
So in other words, need to define CPU cap on the Compute/Service offerings.
Cheers
On Fri, 19 Jul 2019 at 06:44, li jerry <di...@hotmail.com> wrote:
> Hello all
>
> What is the role of the CPU (in MHz) parameter in Compute Offerings?
>
> I created two computing schemes CPU (in MHz) = 500, CPU (in MHz) = 2000
>
> Then two VMs were created through these two computing schemes on top of
> xenserver 7.1.2.
>
> I can't see the difference between these two programs through xencenter.
>
--
Andrija Panić