vMotion from static binding portgroup to NSX segment fails.
search cancel

vMotion from static binding portgroup to NSX segment fails.

book

Article ID: 383567

calendar_today

Updated On:

Products

VMware NSX VMware vSphere ESXi 7.0 VMware vSphere ESXi 8.0 VMware vCenter Server 7.0 VMware vCenter Server 8.0

Issue/Introduction

  • Cross vCenter vMotion from a vDS port group with static binding to an NSX segment may fail when the VM has a vNIC in a disconnected state.
  • In /var/log/hostd.log of the destination ESXi host an error indicating that the source vCenter VDS port could not be found.
<Timestamp> In(166) Hostd[2098771] [Originator@6876 sub=Vimsvc.TaskManager opID=aa3a8045 sid=52c26abe user=vpxuser] Task Completed : haTask--vim.dvs.HostDistributedVirtualSwitchManager.retrieveDVPortgroupConfigSpec-20963246 Status error 
<Timestamp> In(166) Hostd[2098771] [Originator@6876 sub=Solo.Vmomi opID=aa3a8045 sid=52c26abe user=vpxuser] Activation finished; <<########-####-####-####-############, <TCP '127.0.0.1 : 8307'>, <TCP '127.0.0.1 : 31254'>>, ha-hostdvsmanager, vim.dvs.HostDistributedVirtualSwitchManager.retrieveDVPortgroupConfigSpec, <vim.version.v8_0_2_0, internal, 8.0.2.0>, [N11HostdCommon18VmomiAdapterServer19ActivationResponderE:0x000000456bb40f68]> 
<Timestamp> Db(167) Hostd[2098771] [Originator@6876 sub=Solo.Vmomi opID=aa3a8045 sid=52c26abe user=vpxuser] Arg switchUuid: 
<Timestamp> Db(167) Hostd[2098727] --> "50 1f b2 c5 ## ## ## ##-## ## ## ## ## ## ## ##" 
<Timestamp> Db(167) Hostd[2098771] [Originator@6876 sub=Solo.Vmomi opID=aa3a8045 sid=52c26abe user=vpxuser] Arg portgroupKey: 
<Timestamp> Db(167) Hostd[2098727] --> (string) [ 
<Timestamp> Db(167) Hostd[2098727] -->    "dvportgroup-####" 
<Timestamp> Db(167) Hostd[2098727] --> ] 
<Timestamp> In(166) Hostd[2098771] [Originator@6876 sub=Solo.Vmomi opID=aa3a8045 sid=52c26abe user=vpxuser] Throw vim.fault.NotFound 
<Timestamp> In(166) Hostd[2098771] [Originator@6876 sub=Solo.Vmomi opID=aa3a8045 sid=52c26abe user=vpxuser] Result: 
<Timestamp> In(166) Hostd[2098727] --> (vim.fault.NotFound) { 
<Timestamp> In(166) Hostd[2098727] -->    msg = "",  
<Timestamp> In(166) Hostd[2098727] --> }
  • "Failed to get DVS state in the restore phase from the source host" message reported in /var/log/vmkernel.log of destination host:
YYYY-MM-DDTHH:MM:SS.163Z Wa(180) vmkwarning: cpu9:243988946)WARNING: VMotionSend: 3605: 1203585376987067294 D: failed to get DVS state in the restore phase from the source host <vMotion IP> 
YYYY-MM-DDTHH:MM:SS.163Z Wa(180) vmkwarning: cpu9:243988946)WARNING: VMotionSend: 5947: 1203585376987067294 D: Failed handling message reply GET_DVS_STATE: Not found
  • Also, the following error can be found on the destination ESXi host /var/log/hostd.log: 
    <Timestamp> Db(167) Hostd[2101597]: [Originator@6876 sub=Vigor.Vmsvc.vm:/vmfs/volumes/vsan:################-################/########-####-####-####-############/<VM-Name>.vmx] VMotionPrepare: MigrateFromDest message: Failed waiting for data.  Error bad0003. Not found.
    <Timestamp> Db(167) Hostd[2101575]: --> vMotion migration [a011fce:6367199011626985489] failed to get DVS state in the restore phase from the source host <vMotion IP>
    <Timestamp> Db(167) Hostd[2101575]: --> 
    <Timestamp> Db(167) Hostd[2101602]: [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/vsan:################-################/########-####-####-####-############/<VM-Name>.vmx] VMotionStatusCb [6367199011626985489]: Failed with error [N3Vim5Fault20GenericVmConfigFaultE:0x000000afb122a3f0]
    <Timestamp> In(166) Hostd[2101602]: [Originator@6876 sub=Libs] VigorTransportClientManageConnection: connection closed
    <Timestamp> Db(167) Hostd[2101602]: [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/vsan:################-################/########-####-####-####-############/<VM-Name>.vmx] VMotionStatusCb: Firing ResolveCb
    <Timestamp> In(166) Hostd[2101602]: [Originator@6876 sub=Vcsvc.VMotionDst.6367199011626985489] ResolveCb: VMX reports needsUnregister = true for migrateType MIGRATE_TYPE_VMOTION
    <Timestamp> In(166) Hostd[2101602]: [Originator@6876 sub=Vcsvc.VMotionDst.6367199011626985489] ResolveCb: Failed with fault: (vim.fault.GenericVmConfigFault) {
    <Timestamp> In(166) Hostd[2101575]: -->    faultMessage = (vmodl.LocalizableMessage) [
    <Timestamp> In(166) Hostd[2101575]: -->       (vmodl.LocalizableMessage) {
    <Timestamp> In(166) Hostd[2101575]: -->          key = "msg.migrate.waitdata.platform", 
    <Timestamp> In(166) Hostd[2101575]: -->          arg = (vmodl.KeyAnyValue) [
    <Timestamp> In(166) Hostd[2101575]: -->             (vmodl.KeyAnyValue) {
    <Timestamp> In(166) Hostd[2101575]: -->                key = "1", 
    <Timestamp> In(166) Hostd[2101575]: -->                value = "195887107"
    <Timestamp> In(166) Hostd[2101575]: -->             }, 
    <Timestamp> In(166) Hostd[2101575]: -->             (vmodl.KeyAnyValue) {
    <Timestamp> In(166) Hostd[2101575]: -->                key = "2", 
    <Timestamp> In(166) Hostd[2101575]: -->                value = "Not found"
    <Timestamp> In(166) Hostd[2101575]: -->             }
    <Timestamp> In(166) Hostd[2101575]: -->          ], 
    <Timestamp> In(166) Hostd[2101575]: -->          message = "Failed waiting for data.  Error bad0003. Not found.
    <Timestamp> In(166) Hostd[2101575]: --> "
    <Timestamp> In(166) Hostd[2101575]: -->       }, 
    <Timestamp> In(166) Hostd[2101575]: -->       (vmodl.LocalizableMessage) {
    <Timestamp> In(166) Hostd[2101575]: -->          key = "vob.vmotion.dvs.state.restore.failed", 
    <Timestamp> In(166) Hostd[2101575]: -->          arg = (vmodl.KeyAnyValue) [
    <Timestamp> In(166) Hostd[2101575]: -->             (vmodl.KeyAnyValue) {
    <Timestamp> In(166) Hostd[2101575]: -->                key = "1", 
    <Timestamp> In(166) Hostd[2101575]: -->                value = "167845838"
    <Timestamp> In(166) Hostd[2101575]: -->             }, 
    <Timestamp> In(166) Hostd[2101575]: -->             (vmodl.KeyAnyValue) {
    <Timestamp> In(166) Hostd[2101575]: -->                key = "2", 
    <Timestamp> In(166) Hostd[2101575]: -->                value = "6367199011626985489"
    <Timestamp> In(166) Hostd[2101575]: -->             }, 
    <Timestamp> In(166) Hostd[2101575]: -->             (vmodl.KeyAnyValue) {
    <Timestamp> In(166) Hostd[2101575]: -->                key = "3", 
    <Timestamp> In(166) Hostd[2101575]: -->                value = "<vMotion IP>"
    <Timestamp> In(166) Hostd[2101575]: -->             }
    <Timestamp> In(166) Hostd[2101575]: -->          ], 
    <Timestamp> In(166) Hostd[2101575]: -->          message = "vMotion migration [a011fce:6367199011626985489] failed to get DVS state in the restore phase from the source host <vMotion IP>
    <Timestamp> In(166) Hostd[2101575]: --> "
    <Timestamp> In(166) Hostd[2101575]: -->       }
    <Timestamp> In(166) Hostd[2101575]: -->    ], 
    <Timestamp> In(166) Hostd[2101575]: -->    reason = "Failed waiting for data.  Error bad0003. Not found.
    <Timestamp> In(166) Hostd[2101575]: --> ", 
    <Timestamp> In(166) Hostd[2101575]: -->    msg = "Failed waiting for data.  Error bad0003. Not found.
    <Timestamp> In(166) Hostd[2101575]: --> vMotion migration [a011fce:6367199011626985489] failed to get DVS state in the restore phase from the source host <vMotion IP>
    <Timestamp> In(166) Hostd[2101575]: --> "
    <Timestamp> In(166) Hostd[2101575]: --> }

Environment

VMware NSX
VMware vSphere ESXi

Cause

In ESXi, Cross vCenter vMotion may fail if a VM has a vNIC that is disconnected but still attached to a vDS port group configured with static port binding.

Resolution

This is a known issue impacting VMware vSphere ESXi.

Workaround:

  1. Edit Settings of the affected VM.

  2. Connect the virtual machine’s network adapter (vNIC) to the appropriate port group before vMotion migration.

  3. Alternatively, select a DVS portgroup that has port binding set to ephemeral (no-binding).

Additional Information

Powered by Wolken Software