Sailaja Mada created CLOUDSTACK-3466:
----------------------------------------
Summary: [DOC] VM Migration across VMWARE clusters which added
with different switches(StandardSwith,DVS,Nexus) is not supported
Key: CLOUDSTACK-3466
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3466
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Doc
Affects Versions: 4.2.0
Reporter: Sailaja Mada
Steps:
1. Tried migrating VM from VMWARE DVS to Stand Vswitch cluster.
It failed as host added with standard switch does not have VDS .
DVS has cluster scope. Hence migration of VM is supported across cluster with
DVS as the backend vswitch. But if another cluster has vswitch as backend then
we don’t support migration between those clusters with different backend
vswitches
This has to be documented .
Details of the error log :
----------------------------------------------------------------------------------------------------------------------------
2013-07-05 16:08:11,648 DEBUG [cloud.capacity.CapacityManagerImpl]
(Job-Executor-100:job-243) release mem from host: 6, old used:
536870912,reserved: 0, total: 34346127360; new used: 0,reserved:0;
movedfromreserved: false,moveToReserveredfalse
2013-07-05 16:08:11,685 ERROR [cloud.async.AsyncJobManagerImpl]
(Job-Executor-100:job-243) Unexpected exception while executing
org.apache.cloudstack.api.command.admin.vm.MigrateVirtualMachineWithVolumeCmd
com.cloud.utils.exception.CloudRuntimeException: Failed to migrated vm
VM[User|instance2] along with its volumes.
com.cloud.utils.exception.CloudRuntimeException: Error while migrating the vm
VM[User|instance2] to host Host[-6-Routing]. Exception:
java.lang.RuntimeException
Message: Network card 'Network adapter 1' has a DVPort backing, which is not
supported. This could be because the host does not support VDS or because the
host has not joined a VDS.
Stack: java.lang.RuntimeException: Network card 'Network adapter 1' has a
DVPort backing, which is not supported. This could be because the host does not
support VDS or because the host has not joined a VDS.
at
com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:290)
at
com.cloud.hypervisor.vmware.mo.VirtualMachineMO.migrate(VirtualMachineMO.java:329)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:3638)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:420)
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)
at
com.cloud.storage.VolumeManagerImpl.migrateVolumes(VolumeManagerImpl.java:2177)
at
com.cloud.vm.VirtualMachineManagerImpl.migrateWithStorage(VirtualMachineManagerImpl.java:1682)
at
com.cloud.vm.UserVmManagerImpl.migrateVirtualMachineWithVolume(UserVmManagerImpl.java:4035)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
org.apache.cloudstack.api.command.admin.vm.MigrateVirtualMachineWithVolumeCmd.execute(MigrateVirtualMachineWithVolumeCmd.java:137)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
at
com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
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.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-05 16:08:11,686 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-100:job-243) Complete async job-243, jobStatus: 2, resultCode:
530, result: Error Code: 530 Error text: Failed to migrated vm
VM[User|instance2] along with its volumes.
com.cloud.utils.exception.CloudRuntimeException: Error while migrating the vm
VM[User|instance2] to host Host[-6-Routing]. Exception:
java.lang.RuntimeException
Message: Network card 'Network adapter 1' has a DVPort backing, which is not
supported. This could be because the host does not support VDS or because the
host has not joined a VDS.
Stack: java.lang.RuntimeException: Network card 'Network adapter 1' has a
DVPort backing, which is not supported. This could be because the host does not
support VDS or because the host has not joined a VDS.
at
com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:290)
at
com.cloud.hypervisor.vmware.mo.VirtualMachineMO.migrate(VirtualMachineMO.java:329)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:3638)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:420)
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-05 16:08:13,001 DEBUG [cloud.api.ApiServlet] (catalina-exec-3:null)
===START=== 10.144.6.19 -- GET
command=queryAsyncJobResult&jobId=a01d3615-fbe2-4f7e-9131-c3f59337dfae&response=json&sessionkey=qw5mLlCQwn4ujTscAsUpfLYk2xQ%3D&_=1373020877862
2013-07-05 16:08:13,014 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-3:null) Async job-243 completed
2013-07-05 16:08:13,020 DEBUG [cloud.api.ApiServlet] (catalina-exec-3:null)
===END=== 10.144.6.19 -- GET
command=queryAsyncJobResult&jobId=a01d3615-fbe2-4f7e-9131-c3f59337dfae&response=json&sessionkey=qw5mLlCQwn4ujTscAsUpfLYk2xQ%3D&_=1373020877862
--
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
