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
When the deployment goes through, the allocation placement algorithm
will tell you if cpu over provisioning worked. You can see it in
management-server.log file..
Here is an easy way to extract useful info for failed vm deployment.
After deployment failed, grep for cloudstack internal name of
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
