[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13744952#comment-13744952
 ] 

ASF subversion and git services commented on CLOUDSTACK-3851:
-------------------------------------------------------------

Commit a168a5fa2a45e13e2c92933acd81ab8f62c47282 in branch refs/heads/4.2 from 
[~sateeshc]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a168a5f ]

CLOUDSTACK-3851 [VMWare] VM start fails with NPE while trying to retrieve cores 
per socket

If VMware host version is ESXi 4.1 and vCenter version is 5.0 or later, number 
of cores per socket of a VM running on ESXi 4.1 host would be undefined as it's 
not supported for versions prior to 5.0.
Hence expecting undefined/null value for that and handling it.

Signed-off-by: Sateesh Chodapuneedi <[email protected]>

                
> [VMWare] VM start fails with NPE while trying to retrieve cores per socket
> --------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3851
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3851
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>    Affects Versions: 4.2.0
>            Reporter: Likitha Shetty
>            Assignee: Sateesh Chodapuneedi
>            Priority: Critical
>             Fix For: 4.2.0
>
>         Attachments: Logs_DB.rar
>
>
> VM start failed multiple times with the below error,
> 2013-07-23 10:57:16,955 DEBUG [cloud.api.ApiServlet] (catalina-exec-9:null) 
> ===START===  10.252.192.53 -- GET  
> command=queryAsyncJobResult&jobId=05569d7e-8630-4481-a7cf-2d4831ba38fe&response=json&sessionkey=F8Cw9e7dmEvSRFlZRi1DKxUgHPQ%3D&_=1374571983764
> 2013-07-23 10:57:17,023 DEBUG [cloud.api.ApiServlet] (catalina-exec-9:null) 
> ===END===  10.252.192.53 -- GET  
> command=queryAsyncJobResult&jobId=05569d7e-8630-4481-a7cf-2d4831ba38fe&response=json&sessionkey=F8Cw9e7dmEvSRFlZRi1DKxUgHPQ%3D&_=1374571983764
> 2013-07-23 10:57:17,123 DEBUG [vmware.mo.HostMO] (DirectAgent-66:10.147.40.8) 
> find VM i-2-13-VM on host
> 2013-07-23 10:57:17,123 DEBUG [vmware.mo.HostMO] (DirectAgent-66:10.147.40.8) 
> load VM cache on host
> 2013-07-23 10:57:17,135 INFO  [vmware.mo.HypervisorHostHelper] 
> (DirectAgent-66:10.147.40.8) Blank VM: i-2-13-VM is ready for use
> 2013-07-23 10:57:17,135 DEBUG [vmware.mo.HostMO] (DirectAgent-66:10.147.40.8) 
> find VM i-2-13-VM on host
> 2013-07-23 10:57:17,135 DEBUG [vmware.mo.HostMO] (DirectAgent-66:10.147.40.8) 
> VM i-2-13-VM found in host cache
> 2013-07-23 10:57:17,408 WARN  [vmware.resource.VmwareResource] 
> (DirectAgent-66:10.147.40.8) StartCommand failed due to Exception: 
> java.lang.NullPointerException
> Message: null
> java.lang.NullPointerException
>       at 
> com.cloud.hypervisor.vmware.mo.VirtualMachineMO.getCoresPerSocket(VirtualMachineMO.java:2203)
>       at 
> com.cloud.hypervisor.vmware.mo.VirtualMachineMO.isCpuHotAddSupported(VirtualMachineMO.java:2244)
>       at 
> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2598)
>       at 
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:520)
>       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-07-23 10:57:17,413 DEBUG [agent.manager.DirectAgentAttache] 
> (DirectAgent-66:null) Seq 6-1231552610: Response Received: 
> 2013-07-23 10:57:17,415 DEBUG [agent.transport.Request] (DirectAgent-66:null) 
> Seq 6-1231552610: Processing:  { Ans: , MgmtId: 7635042566263, via: 6, Ver: 
> v1, Flags: 10, 
> [{"com.cloud.agent.api.StartAnswer":{"vm":{"id":13,"name":"i-2-13-VM","bootloader":"HVM","type":"User","cpus":1,"minSpeed":500,"maxSpeed":500,"minRam":536870912,"maxRam":536870912,"arch":"x86_64","os":"CentOS
>  5.3 
> (64-bit)","bootArgs":"","rebootOnCrash":false,"enableHA":false,"limitCpuUse":false,"enableDynamicallyScaleVm":false,"vncPassword":"1e2cc9569b294009","params":{"nicAdapter":"E1000","enable.dynamic.scaling":"false","nestedVirtualizationFlag":"false","rootDiskController":"ide"},"uuid":"a92658ea-5534-4b40-a066-9bc9b2a5a607","disks":[{"data":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"a3ac26fc-92da-476c-8e45-c2421e24e041","volumeType":"ROOT","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"bd186911-97af-371a-9b26-fac999fc98a4","id":2,"poolType":"NetworkFilesystem","host":"10.147.28.7","path":"/export/home/prashant/primary2","port":2049}},"name":"ROOT-13","size":0,"path":"ROOT-13-16","volumeId":16,"vmName":"i-2-13-VM","accountId":2,"format":"OVA","id":16}},"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":"c45371b8-0535-4155-b57b-cbc28c712fab","ip":"10.1.1.220","netmask":"255.255.255.0","gateway":"10.1.1.1","mac":"02:00:71:0c:00:03","dns1":"10.103.128.16","broadcastType":"Vlan","type":"Guest","broadcastUri":"vlan://1106","isolationUri":"vlan://1106","isSecurityGroupEnabled":false}]},"result":false,"details":"StartCommand
>  failed due to Exception: java.lang.NullPointerException\nMessage: 
> null\n","wait":0}}] }

--
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

Reply via email to