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

  • vMotion from static binding portgroup to NSX segment fails.
  • Source vNIC of attempted VM is disconnected from the portgroup.
  • The destination hostd log show an error stating that the source VC VDS port cannot be found.
2024-10-18T00:48:47.853Z 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 
2024-10-18T00:48:47.853Z In(166) Hostd[2098771] [Originator@6876 sub=Solo.Vmomi opID=aa3a8045 sid=52c26abe user=vpxuser] Activation finished; <<52c26abe-bf59-db37-795e-40f486839eb6, <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]> 
2024-10-18T00:48:47.853Z Db(167) Hostd[2098771] [Originator@6876 sub=Solo.Vmomi opID=aa3a8045 sid=52c26abe user=vpxuser] Arg switchUuid: 
2024-10-18T00:48:47.853Z Db(167) Hostd[2098727] --> "50 1f b2 c5 ## ## ## ##-## ## ## ## ## ## ## ##" 
2024-10-18T00:48:47.853Z Db(167) Hostd[2098771] [Originator@6876 sub=Solo.Vmomi opID=aa3a8045 sid=52c26abe user=vpxuser] Arg portgroupKey: 
2024-10-18T00:48:47.853Z Db(167) Hostd[2098727] --> (string) [ 
2024-10-18T00:48:47.853Z Db(167) Hostd[2098727] -->    "dvportgroup-####" 
2024-10-18T00:48:47.853Z Db(167) Hostd[2098727] --> ] 
2024-10-18T00:48:47.853Z In(166) Hostd[2098771] [Originator@6876 sub=Solo.Vmomi opID=aa3a8045 sid=52c26abe user=vpxuser] Throw vim.fault.NotFound 
2024-10-18T00:48:47.853Z In(166) Hostd[2098771] [Originator@6876 sub=Solo.Vmomi opID=aa3a8045 sid=52c26abe user=vpxuser] Result: 
2024-10-18T00:48:47.853Z In(166) Hostd[2098727] --> (vim.fault.NotFound) { 
2024-10-18T00:48:47.853Z In(166) Hostd[2098727] -->    msg = "",  
2024-10-18T00:48:47.853Z In(166) Hostd[2098727] --> }
  • "failed to get DVS state in the restore phase from the source host ..." message is output in vmkernel log of destination host.
2024-10-18T00:49:03.163Z Wa(180) vmkwarning: cpu9:243988946)WARNING: VMotionSend: 3605: 1203585376987067294 D: failed to get DVS state in the restore phase from the source host <##.##.##.##> 
2024-10-18T00:49:03.163Z Wa(180) vmkwarning: cpu9:243988946)WARNING: VMotionSend: 5947: 1203585376987067294 D: Failed handling message reply GET_DVS_STATE: Not found

Environment

VMware NSX

VMware ESXi 7.x, 8.x

Cause

There is a bug in the code for vMotion.

 

Resolution

This issue will be fixed in a future release of ESXi.

For workaround, connect the vNIC to the portgroup for the vMotion or use an ephemeral (no binding) portgroup.

 

Additional Information

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

vMotion across switch fails with NSX segment.
https://knowledge.broadcom.com/external/article/389032

Powered by Wolken Software