cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Animesh Chaturvedi (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-4512) [VMWARE] Deployment of User VM Fails on the ESXi host due to CPU Resources unavailability
Date Thu, 07 Nov 2013 22:05:19 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-4512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Animesh Chaturvedi updated CLOUDSTACK-4512:
-------------------------------------------

    Fix Version/s:     (was: 4.3.0)
                   Future

BULK EDIT> Moving the unassigned features and improvements out of 4.3

> [VMWARE] Deployment of User VM Fails on the ESXi host due to CPU Resources unavailability
> -----------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4512
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4512
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server, VMware
>    Affects Versions: 4.2.0
>            Reporter: Chandan Purushothama
>             Fix For: Future
>
>         Attachments: hostd.zip, management-server.zip
>
>
> ================
> Steps to Reproduce:
> ================
> 1. Deploy a VM using the default CentOS Template.
> ===========
> Observation:
> ===========
> Observe that the error complains about CPU Resources on the ESXi host, while the host
has more than enough CPU Resources to service the VM.
> On the Management Server Log:
> 2013-08-26 16:01:51,808 WARN  [vmware.resource.VmwareResource] (DirectAgent-151:10.223.57.66)
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.
>         at com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:378)
>         at com.cloud.hypervisor.vmware.mo.VirtualMachineMO.powerOn(VirtualMachineMO.java:188)
>         at com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:3099)
>         at com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:514)
>         at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
>         at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>         at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
>         at java.util.concurrent.FutureTask.run(FutureTask.java:166)
>         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
>         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
>         at java.lang.Thread.run(Thread.java:679)
> 2013-08-26 16:01:51,812 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-151:null)
Seq 5-746390325: Response Received:
> 2013-08-26 16:01:51,814 DEBUG [agent.transport.Request] (DirectAgent-151:null) Seq 5-746390325:
Processing:  { Ans: , MgmtId: 7471666038533, via: 5, Ver: v1, Flags: 10, [{"com.cloud.agent.api.StartAnswer":{"vm":{"id":27,"name":"i-9-27-VMWARERETEST","bootloader":"HVM","type":"User","cpus":1,"minSpeed":500,"maxSpeed":500,"minRam":536870912,"maxRam":536870912,"hostName":"Boron-VM-1","arch":"x86_64","os":"CentOS
5.3 (64-bit)","bootArgs":"","rebootOnCrash":false,"enableHA":false,"limitCpuUse":false,"enableDynamicallyScaleVm":false,"vncPassword":"f12649cca76b879d","params":{"rootDiskController":"ide","nicAdapter":"E1000","nestedVirtualizationFlag":"false"},"uuid":"79201226-48cf-43d9-9d20-50a3a8d4c7aa","disks":[{"data":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"d0467aeb-0774-4aaa-99cd-80a4843d7ffd","volumeType":"ROOT","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"96bc10ee-70b3-3d20-a60c-c068a024b3a7","id":201,"poolType":"NetworkFilesystem","host":"10.223.110.232","path":"/export/home/chandan/307PB-195-103/primary2","port":2049}},"name":"ROOT-27","size":2147483648,"path":"ROOT-27","volumeId":38,"vmName":"i-9-27-VMWARERETEST","accountId":9,"format":"OVA","id":38,"hypervisorType":"VMware"}},"diskSeq":0,"type":"ROOT"},{"data":{"org.apache.cloudstack.storage.to.TemplateObjectTO":{"id":0,"format":"ISO","accountId":0,"hvm":false}},"diskSeq":3,"type":"ISO"}],"nics":[{"deviceId":0,"networkRateMbps":200,"defaultNic":true,"uuid":"2ce1f4ba-2420-4060-81bd-da30ef53fcd9","ip":"10.1.1.157","netmask":"255.255.255.0","gateway":"10.1.1.1","mac":"02:00:74:1d:00:01","dns1":"8.8.8.8","dns2":"8.8.4.4","broadcastType":"Vlan","type":"Guest","broadcastUri":"vlan://2600","isolationUri":"vlan://2600","isSecurityGroupEnabled":false}]},"result":false,"details":"StartCommand
failed due to Exception: java.lang.RuntimeException\nMessage: The available CPU resources
in the parent resource pool are insufficient for the operation.\n","wait":0}}] }
> 2013-08-26 16:01:51,814 DEBUG [agent.transport.Request] (Job-Executor-25:job-125 = [
bb63450c-35de-4f1f-b81b-1ac34777782f ]) Seq 5-746390325: Received:  { Ans: , MgmtId: 7471666038533,
via: 5, Ver: v1, Flags: 10, { StartAnswer } }
> 2013-08-26 16:01:51,820 INFO  [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-25:job-125
= [ bb63450c-35de-4f1f-b81b-1ac34777782f ]) Unable to start VM on Host[-5-Routing] due to
StartCommand failed due to Exception: java.lang.RuntimeException
> Message: The available CPU resources in the parent resource pool are insufficient for
the operation.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message