vMotion across switch fails with NSX segment.

Products

• VMware vSphere ESXi 7.0
• VMware vSphere ESXi 8.0
• VMware vCenter Server 8.0
• VMware vCenter Server 7.0

Issue/Introduction

• Cross-switch vMotion of virtual machines with NSX segments configured at source and destination fails.

• Failed to get DVS state with “Failed waiting for data. Error bad0001. Failure.” message in hostd log on destination ESXi host

  yyyy-mm-ddT00:00:00.000Z verbose hostd[12345] [Originator@6876 sub=Vigor.Vmsvc.vm:/vmfs/volumes/iscsi-1/test-vm.vmx opID=m48tsdf-auto-t7ab-h5:700000-00-00-00-abcd] VMotionPrepare: MigrateFromDest message: Failed waiting for data.  Error bad0001. Failure.
--> vMotion migration [abcdefg:1234567890] failed to get DVS state in the restore phase from the source host <xx.xx.xx.xx>
-->

• GET_DVS_STATE: Failure.” message in vmkernel log on destination ESXi host
  
  yyyy-mm-ddT00:00:00.000Z cpu11:123456)WARNING: VMotionSend: 5896: 123456789012345 D: Failed handling message reply GET_DVS_STATE: Failure

 

Environment

VMware NSX
VMware vSphere ESXi 7.x, 8.x

Cause

There is a bug in the code for vMotion.

Resolution

Fixed in ESXi 8.0 U1 or later

For workaround, connect the vNICs before performing vMotion.

Additional Information

KB383567 is a similar issue, but with slightly different log messages and conditions.

vMotion from static binding portgroup to NSX segment fails.
https://knowledge.broadcom.com/external/article/383567/vmotion-from-static-binding-portgroup-to.html