You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Venkata Siva Vijayendra Bhamidipati (JIRA)" <ji...@apache.org> on 2013/07/09 21:51:49 UTC
[jira] [Commented] (CLOUDSTACK-3425) Vmware - Not able to deploy VM
- Router Vm fails to start.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13703708#comment-13703708 ]
Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-3425:
-----------------------------------------------------------------
I hit the same issue on latest master but with a slightly different error message but with the same stack trace:
WARN [vmware.resource.VmwareResource] (DirectAgent-13:10.223.251.130) StartCommand failed due to Exception: java.lang.RuntimeException
Message: A specified parameter was not correct.
java.lang.RuntimeException: A specified parameter was not correct.
at com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:290)
at com.cloud.hypervisor.vmware.mo.VirtualMachineMO.configureVm(VirtualMachineMO.java:833)
at com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2842)
at com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:508)
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:1146)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
INFO [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-13:job-13) Unable to start VM on Host[-1-Routing] due to StartCommand failed due to Exception: java.lang.RuntimeException
Message: A specified parameter was not correct.
Looking at the ESX logs the problem was that two of the five vNICs being plumbed on the router VM when bringing it up didn't have the uuid of the nicira NVP interfaces set, so ESX threw the above fault.
Will put up a fix for review. Hugo, please review the fix since I'm not sure whether you need all the five interfaces to be plumbed as nvp interfaces on the router VM or whether simply having only those that have their uuids set will suffice. Does the NVP code path on the mgmt server assume somewhere that these two additional unused nvp interfaces exist on the VR? If so, we'll need to make changes to those parts as well.
> Vmware - Not able to deploy VM - Router Vm fails to start.
> ----------------------------------------------------------
>
> Key: CLOUDSTACK-3425
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3425
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Management Server
> Affects Versions: 4.2.0
> Environment: Build from 4.2
> Reporter: Sangeetha Hariharan
> Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: management-server.log
>
>
> Vmware - Not able to deploy VM - Router Vm fails to start.
> Steps to reproduce the problem:
> Advanced zone set up with vmware 5.0 host.
> Once the zone is configured and enabled , system Vms come up successfully.
> Default template gets downloaded.
> Try to deploy a new VM.
> VM deployment fails because of the router VM not being able to start successfully.
> Router is in stopped state.
> Trying to start the router manually also fails.
> Following exception seen when start command is issued for Router :
> 2013-07-09 10:40:15,805 INFO [vmware.mo.HypervisorHostHelper] (DirectAgent-158:10.223.57.66) Network cloud.public.1371.0.1-vSwitch0 is ready on vSwitch vSwitch0
> 2013-07-09 10:40:15,854 INFO [vmware.resource.VmwareResource] (DirectAgent-158:10.223.57.66) Preparing NIC device on network cloud.public.1371.0.1-vSwitch0
> 2013-07-09 10:40:15,855 DEBUG [vmware.resource.VmwareResource] (DirectAgent-158:10.223.57.66) Prepare NIC at new device {"operation":"ADD","device":{"addressType":"Manual","macAddress":"02:00:0e:fc:00:04","key":-7,"backing":{"network":{"value":"network-30877","type":"Network"},"deviceName":"cloud.public.1371.0.1-vSwitch0"},"connectable":{"startConnected":true,"allowGuestControl":true,"connected":true},"unitNumber":4}}
> 2013-07-09 10:40:15,855 DEBUG [vmware.mo.HostMO] (DirectAgent-158:10.223.57.66) find VM r-4-VM on host
> 2013-07-09 10:40:15,855 DEBUG [vmware.mo.HostMO] (DirectAgent-158:10.223.57.66) VM r-4-VM found in host cache
> 2013-07-09 10:40:15,871 INFO [vmware.resource.VmwareResource] (DirectAgent-158:10.223.57.66) Configure VNC port for VM r-4-VM, port: 5962, host: 10.223.57.66
> 2013-07-09 10:40:15,949 DEBUG [agent.manager.AgentManagerImpl] (AgentManager-Handler-14:null) Ping from 2
> 2013-07-09 10:40:16,452 WARN [vmware.resource.VmwareResource] (DirectAgent-158:10.223.57.66) StartCommand failed due to Exception: java.lang.RuntimeException
> Message: Invalid configuration for device '0'.
> java.lang.RuntimeException: Invalid configuration for device '0'.
> at com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:290)
> at com.cloud.hypervisor.vmware.mo.VirtualMachineMO.configureVm(VirtualMachineMO.java:833)
> at com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2842)
> at com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:508)
> 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-09 10:40:16,454 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-158:null) Seq 1-397543353: Cancelling because one of the answers is false and it is stop on error.
--
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