On Wed, Jan 8, 2014 at 3:29 PM, Hollman Enciso R.
hollman.enc...@gmail.com wrote:
x3 has 3 cores 3gb of ram, 3.00 GHz
Do your hypervisors support this?
On Wed, Jan 8, 2014 at 9:47 AM, Daan Hoogland daan.hoogl...@gmail.comwrote:
Do your hypervisors support this?
Yes.
I made a test creating a new VM directly on the hypervisor with the same
resources (x3) and work ok
--
Hollman Eduardo Enciso R.
http://nexxuz.com
http://algolibre.com
On Wed, Jan 8, 2014 at 3:47 PM, Daan Hoogland daan.hoogl...@gmail.comwrote:
On Wed, Jan 8, 2014 at 3:29 PM, Hollman Enciso R.
hollman.enc...@gmail.com wrote:
x3 has 3 cores 3gb of ram, 3.00 GHz
Do your hypervisors support this?
As Daan said, check that your hypervisors report the CPUs
On Wed, Jan 8, 2014 at 10:05 AM, Erik Weber terbol...@gmail.com wrote:
As Daan said, check that your hypervisors report the CPUs are 3.00GHz or
more and not something like 2.99GHz.
I had a similar issue where 2.0GHz CPUs actually reported with a speed of
1.99GHz and subsequently my 2GHz
Comments inline.
On 08-Jan-2014, at 8:40 pm, Hollman Enciso R. hollman.enc...@gmail.com wrote:
On Wed, Jan 8, 2014 at 10:05 AM, Erik Weber terbol...@gmail.com wrote:
As Daan said, check that your hypervisors report the CPUs are 3.00GHz or
more and not something like 2.99GHz.
I had a
It looks like your host is in an avoid set and cannot be used for
deploying new vms.
1.
2014-01-0809:10:42,798DEBUG[cloud.deploy.FirstFitPlanner](Job-Executor-5:job-43=[84f54047-8d50-47c0-b251-bb2798378806])Listing
clusters in order of aggregate capacity, that have(atleast one host
Dave.
Thanks a lot.
the problem was that x3, x4 ... was created with 3 and 4 GHz. but my
hypervisor just support 2.4 GHz
Problem solved
On Wed, Jan 8, 2014 at 10:43 AM, Dave Hoffman david.hoff...@appcore.comwrote:
It looks like your host is in an avoid set and cannot be used for
deploying
On 08-Jan-2014, at 9:43 pm, Hollman Enciso R. hollman.enc...@gmail.com wrote:
On Wed, Jan 8, 2014 at 10:49 AM, Shanker Balan
shanker.ba...@shapeblue.comwrote:
Specifying the CPU speed with CPU cap becomes problematic if you have
different clusters with different speed ratings.
Am not sure