[
https://issues.apache.org/jira/browse/CLOUDSTACK-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13615787#comment-13615787
]
Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-1822:
-----------------------------------------------------------------
Prashant,
In vCenter (you can refer to the same screenshot you posted - hidden behind the
error dialog), what values do the CPU related fields "Total capacity",
"Reserved capacity" and "Available capacity" show? vCenter would throw an
exception if it failed to power on the VM due to whatever reason, so it's fine
to encounter an exception. But yes the 5GHz value looks like it may be invalid
if the available CPU is less than 5GHz.
> Failed to deploy vm on vmware with service offering {CPU
> =5GHZ,RAM=1024M};StartCommand failed due to Exception:
> java.lang.RuntimeException Message: Failed to power on VM.; CPU min outside
> valid range
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-1822
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1822
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.2.0
> Reporter: prashant kumar mishra
> Assignee: Venkata Siva Vijayendra Bhamidipati
> Priority: Critical
> Fix For: 4.2.0
>
> Attachments: management-server.log, screenshot-1.jpg
>
>
> Tried to Deploy a vm with service offering having 5 GHz CPU and 1024 MB RAM,
> Deployment failed because cant not power on VM
> Note->Host is having enough capacity .
> My observation
> -----------------------
> Able to deploy vm with Service offering {CPU=500MHz,1000MHz,2000MHz, and RAM
> 1024MB}
> Vcenter message
> -------------------------
> An error was received from the ESX host while powering on VM i-2-20-VM.
> Failed to power on VM.
> Could not power on VM : CPU min outside valid range.
> Group host/user: Invalid CPU allocation requested for VM vmm0:i-2-20-VM.
> (min: 5000 mhz, max: -1, minLimit: -1, shares: -1)
> SharedArea: Unable to find 'testSharedAreaPtr' in SHARED_PER_VM_VMX area.
> ----------------------------------------------------------------
> LOG
> ----------
> ----------
> 2013-03-27 04:54:23,630 WARN [vmware.resource.VmwareResource]
> (DirectAgent-121:10.147.40.8) StartCommand failed due to Exception:
> java.lang.RuntimeException
> Message: Failed to power on VM.
> java.lang.RuntimeException: Failed to power on VM.
> at
> com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:291)
> at
> com.cloud.hypervisor.vmware.mo.VirtualMachineMO.powerOn(VirtualMachineMO.java:184)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2351)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:432)
> 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-03-27 04:54:23,635 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-121:null) Seq 1-381878429: Response Received:
> 2013-03-27 04:54:23,638 DEBUG [agent.transport.Request]
> (DirectAgent-121:null) Seq 1-381878429: Processing: { Ans: , MgmtId:
> 7564947357731, via: 1, Ver: v1, Flags: 110,
> [{"StartAnswer":{"vm":{"id":20,"name":"i-2-20-VM","bootloader":"HVM","type":"User","cpus":1,"minSpeed":5000,"maxSpeed":5000,"minRam":1073741824,"maxRam":1073741824,"arch":"x86_64","os":"CentOS
> 5.3
> (64-bit)","bootArgs":"","rebootOnCrash":false,"enableHA":false,"limitCpuUse":false,"vncPassword":"3a7b2be99e84ee0c","params":{"rootDiskController":"ide","nicAdapter":"E1000"},"uuid":"aa8263ce-43dc-4f2c-a6ad-18d58bd1f079","disks":[{"id":27,"name":"ROOT-20","mountPoint":"/export/home/prashant/kvmp1","path":"ROOT-20-27","size":2147483648,"type":"ROOT","storagePoolType":"NetworkFilesystem","storagePoolUuid":"091b14bf-a730-3f12-b955-1097b32907b2","deviceId":0},{"id":20,"name":"CentOS
> 5.3(64-bit) no GUI
> (vSphere)","size":0,"type":"ISO","storagePoolType":"ISO","deviceId":3}],"nics":[{"deviceId":0,"networkRateMbps":200,"defaultNic":true,"uuid":"b0528f80-4710-4d6d-a2d5-d2c2c3fcf507","ip":"10.1.1.65","netmask":"255.255.255.0","gateway":"10.1.1.1","mac":"02:00:66:99:00:12","dns1":"10.103.128.16","broadcastType":"Vlan","type":"Guest","broadcastUri":"vlan://1104","isolationUri":"vlan://1104","isSecurityGroupEnabled":false}]},"result":false,"details":"StartCommand
> failed due to Exception: java.lang.RuntimeException\nMessage: Failed to
> power on VM.\n","wait":0}}] }
> 2013-03-27 04:54:23,639 DEBUG [agent.transport.Request]
> (Job-Executor-7:job-70) Seq 1-381878429: Received: { Ans: , MgmtId:
> 7564947357731, via: 1, Ver: v1, Flags: 110, { StartAnswer } }
> 2013-03-27 04:54:23,646 DEBUG [agent.manager.AgentAttache]
> (DirectAgent-121:null) Seq 1-381878429: No more commands found
> 2013-03-27 04:54:23,655 INFO [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-7:job-70) Unable to start VM on Host[-1-Routing] due to
> StartCommand failed due to Exception: java.lang.RuntimeException
> Message: Failed to power on VM.
> 2013-03-27 04:54:23,666 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-7:job-70) Cleaning up resources for the vm VM[User|five] in
> Starting state
> 2013-03-27 04:54:23,671 DEBUG [agent.transport.Request]
> (Job-Executor-7:job-70) Seq 1-381878430: Sending { Cmd , MgmtId:
> 7564947357731, via: 1, Ver: v1, Flags: 100111,
> [{"StopCommand":{"isProxy":false,"vmName":"i-2-20-VM","wait":0}}] }
> 2013-03-27 04:54:23,671 DEBUG [agent.transport.Request]
> (Job-Executor-7:job-70) Seq 1-381878430: Executing: { Cmd , MgmtId:
> 7564947357731, via: 1, Ver: v1, Flags: 100111,
> [{"StopCommand":{"isProxy":false,"vmName":"i-2-20-VM","wait":0}}] }
> 2013-03-27 04:54:23,672 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-123:null) Seq 1-381878430: Executing request
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
