Details
Description
->For vmware cluster(with only one host) vcenter shows total capacity of cluster is (Memory 13431 MB, CPU 7752MHz) which is available for vm deployment and cloud stack shows (Memory 15.99 GB, CPU 9572) .
->Due to this calculation difference CS allocator shows capacity is available on host but vm deployment fails with run time error
"2013-06-13 12:23:01,945 WARN [vmware.resource.VmwareResource] (DirectAgent-141:10.147.40.7) StartCommand failed due to Exception: java.lang.RuntimeException
Message: The available CPU resources in the parent resource pool are insufficient for the operation.
java.lang.RuntimeException: The available CPU resources in the parent resource pool are insufficient for the operation.
"
DB
mysql> select *from op_host_capacity where capacity_type in (0,1)\G;
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 1. row ***************************
id: 1
host_id: 1
data_center_id: 1
pod_id: 1
cluster_id: 1
used_capacity: 6039797760
reserved_capacity: 0
total_capacity: 17169539072
capacity_type: 0
capacity_state: Enabled
update_time: 2013-06-13 15:29:33
created: 2013-06-05 16:05:51 - 2. row ***************************
id: 2
host_id: 1
data_center_id: 1
pod_id: 1
cluster_id: 1
used_capacity: 7700
reserved_capacity: 0
total_capacity: 9572
capacity_type: 1
capacity_state: Enabled
update_time: 2013-06-13 15:29:33
created: 2013-06-05 16:05:51
2 rows in set (0.00 sec)
- 1. row ***************************
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Attachments
Attachments
Issue Links
- is duplicated by
-
CLOUDSTACK-2124 VM Deployment Failure on VMWare ESXi Host: StartCommand failed due to java.lang.RuntimeException
- Resolved
- is required by
-
CLOUDSTACK-2985 Scaling up cpu is not triggering live migration
- Closed
- supercedes
-
CLOUDSTACK-2985 Scaling up cpu is not triggering live migration
- Closed