changing the network and the host of a virtual machine during vmotion is not supported

[tdubb123]

any idea why I am getting this error? I a m trying to vmotion a running vm from one cluster to another without shared storage.

[adamwiso]

Couple questions on your vMotion network configuration.
1) Are you using the vMotion network TCP/IP stack?

2) If so, do you have L3 gateway defined for your vMotion network?

[tdubb123]

1. YEs

2. Yes it is defined.

[tdubb123]

any idea? Both source and destination host are on the same vlan but different cluster. They are both in same vcenter and datacenter

[bspagna89]

Hi,

Can you give us some insight on how your virtual switch or dvswitch is setup? If you are using regular switches please make sure that the portgroup configuration matches on both servers. If this is a virtual distributed switch, please make sure the destination server has the correct VLANs trunked. Are you migrating to hosts that are running different switches? For example, if source host is running VDS, I believe you cannot migrate back to regular vSwitch during a vMotion.

[tdubb123]

not sure if this is the problem. source host is esxi 5.0

destination is 6.0

[JMachieJr]

vSphere 5.1 and higher supports vMotion across clusters without shared storage. If your source host is 5.0 that's why you are getting those error messages.

[tdubb123]

yes. after upgrading the host to 5.5, vmotion across the clusters work. One thing I had to do too was to rename my destination VM port group to the same as the source.

looks like it doesnt like a different name

[JMachieJr]

Sorry I didn't reply sooner. Didn't see the notification until now. Yes your port group name must match in order for it to do a live migration. What I have done is create a port group named TemplateHolder that exist on every ESXi host that we use for new VM's being deployed. It has no network connectivity but it's useful for when I want to move a VM to a new cluster with different networking. I just change the port group to TemplateHolder then change it to the new port group in the other cluster after the vmotion completes.

[RAJ_RAJ]

HI ,

upgrade to esxi 5.5 and doing vmotion will work  but as you said  need same port groups  /  vmtion should be enabled /  and  both host should have vmotion communication