vMotion across switch fails with NSX segment: "failed to get DVS state in the restore phase from the source host"

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 fails when NSX segments are configured at both the source and destination.
• The virtual network interface card (vNIC) on the source virtual machine is in a disconnected state.
• The /var/run/log/hostd.log on the destination ESXi host reports a failure to retrieve the Distributed Virtual Switch (DVS) state, displaying the following errors:

  <timestamps> verbose hostd[12345] [Originator@6876 sub=Vigor.Vmsvc.vm:/vmfs/volumes/#####/#####.vmx opID=#######-####-####-##:######-##-##-##-####] VMotionPrepare: MigrateFromDest message: Failed waiting for data.  Error bad0001. Failure.
  --> vMotion migration [######:######] failed to get DVS state in the restore phase from the source host <###.###.###.###>
  -->

• The /var/run/log/vmkernel.log on the destination ESXi host reports the following error:
  

  <timestamps> cpu11:123456)WARNING: VMotionSend: 5896: ########## D: Failed handling message reply GET_DVS_STATE: Failure

Environment

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

Resolution

This issue is resolved in VMware ESXi 8.0 Update 1, available at Broadcom downloads.

If you are having difficulty finding and downloading software, please review the Download Broadcom products and software KB.

Workaround:

1. Edit the virtual machine settings on the source host.
2. Connect the vNIC(s) that are currently in a disconnected state.
3. Perform the cross-switch vMotion.

Additional Information

For environments experiencing vMotion failures with slightly different log messages and conditions, please refer to KB: vMotion from static binding portgroup to NSX segment fails.

Japanese version: NSX セグメントを使用した仮想スイッチをまたぐ vMotion が「ソースホスト<#.#.#.#>からリストアフェーズの Distributed Switch状態を取得できませんでした。」のエラーで失敗する