It's enough to raised CPU overprovisioning factor only on the cluster level (assuming 4.11). NO need to restart mgmt at all (though it says it's needed...) NO need to restart any hypervisors hosts In order for correct changes to happen, you need to stop and start all the running VMs (in KVM they will get less CPU shares, in VMware it depends - if reservations are active, then it will get less reservations, in XenServer it will change weigh of each VM's CPU, etc) - AND correct MHz numbers will be displayed only once you stop/start all running VMs. Number of cores can't be overprovisioned - doesn't change in the UI/CloudStack
Best Andrija On Thu, 27 Jun 2019 at 11:57, Fariborz Navidan <mdvlinqu...@gmail.com> wrote: > Hello All, > > I have raised the cpu over provisioning factor in both global and cluster > settings and rebooted both management and server and host. The result is > that the factor is only applied on cpu frequency capacity but not on # of > cores. Please advise about that. > > Best Regards. > -- Andrija Panić
