012 2:31 PM
To: cloudstack-dev@incubator.apache.org
Subject: RE: CPU CAP XenServer
Hi Matthew,
That's a very good question, thanks for bringing this up.
When we implemented cap/weight for XenServer, we thought cap/weight is
per VCPU not per VM.
If cap is wrong, then weight is also wron
nal Message-
> From: Anthony Xu [mailto:xuefei...@citrix.com]
> Sent: Thursday, June 14, 2012 2:31 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: CPU CAP XenServer
>
> Hi Matthew,
>
> That's a very good question, thanks for bringing this up.
> When we i
with definite answer.
Anthony
> -Original Message-
> From: Matthew Hartmann [mailto:mhartm...@tls.net]
> Sent: Thursday, June 14, 2012 7:33 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: CPU CAP XenServer
>
> Hello:
>
> I reported this issue as a bug
Hello:
I reported this issue as a bug way back when 2.2.13 was released and it
has yet to be resolved. It still exists as a bug even in 3.0.2.
http://bugs.cloudstack.org/browse/CS-12972
Please feel free to submit your comments to the bug report.
Cheers,
Matthew
On 6/14/2012 10:26 AM, Dieg
Hi, i found a issue and want know that it's a real issue.
I've created a service offering with CPU CAP enabled and after deployment
i figured out that cap might be wrong.
Host: Intel(R) Xeon(R) CPU E5-2630 0 @ 2.30GHz
Service Offering: 4 x 2.0 GHz
VM:VCPUs-params (MRW): weight: 220;
