vNIC disconnected after vSphere HA failover or vMotion and reconnecting vNIC fails with error: Failed to connect virtual device ethernetX
search cancel

vNIC disconnected after vSphere HA failover or vMotion and reconnecting vNIC fails with error: Failed to connect virtual device ethernetX

book

Article ID: 318972

calendar_today

Updated On:

Products

VMware vCenter Server VMware vSphere ESXi

Issue/Introduction

  • After initiating vSphere HA failover, some of the VMs are powered on with vNIC disconnected to vDS
  • Reconnecting vNIC fails with error:
    Failed to connect virtual device ethernetX
  • In the vmware.log file, you can see entries similar to:

    YYYY-MM-DDTHH:MM:SSZ vcpu-0| I125: PIIX4: PM Resuming from suspend type 0x0, chipset.onlineStandby 1 
    YYYY-MM-DDTHH:MM:SSZ| vcpu-0| I125: VMXNET3 user: failed to connect Ethernet2 to DV Port 197. 
    YYYY-MM-DDTHH:MM:SSZ| vcpu-0| I125: Msg_Post: Warning 
    YYYY-MM-DDTHH:MM:SSZ| vcpu-0| I125: [msg.device.startdisconnected] Virtual device Ethernet2 will start disconnected. YYYY-MM-DDTHH:MM:SSZ| vcpu-0| I125: ----------------------------------------
    YYYY-MM-DDTHH:MM:SSZ| vcpu-0| I125: Vigor_MessageRevoke: message 'msg.device.startdisconnected' (seq 32888121) is revoked 
    YYYY-MM-DDTHH:MM:SSZ| vcpu-0| I125: VMXNET3 user: failed to connect Ethernet1 to DV Port 13. YYYY-MM-DDTHH:MM:SSZ| vcpu-0| I125: Msg_Post: Warning YYYY-MM-DDTHH:MM:SSZ| vcpu-0| I125: [msg.device.startdisconnected] Virtual device Ethernet1 will start disconnected. 
    YYYY-MM-DDTHH:MM:SSZ| vcpu-0| I125: ---------------------------------------- YYYY-MM-DDTHH:MM:SSZ| vcpu-0| I125: Vigor_MessageRevoke: message 'msg.device.startdisconnected' (seq 32888122) is revoked 
    YYYY-MM-DDTHH:MM:SSZ| vcpu-0| I125: VMXNET3 user: failed to connect Ethernet0 to DV Port 124. 
    YYYY-MM-DDTHH:MM:SSZ| vcpu-0| I125: Msg_Post: Warning YYYY-MM-DDTHH:MM:SSZ| vcpu-0| I125: [msg.device.startdisconnected] Virtual device Ethernet0 will start disconnected. 
    YYYY-MM-DDTHH:MM:SSZ| vcpu-0| I125: ---------------------------------------- 
    YYYY-MM-DDTHH:MM:SSZ| vcpu-0| I125: Vigor_MessageRevoke: message 'msg.device.startdisconnected' (seq 32888123) is revoked


  • In the /var/run/log/vpxa.log file, you see entries similar to:

    YYYY-MM-DDTHH:MM:SSZ verbose vpxa[FFEC8B70] [Originator@6876 sub=MoDvs opID=70b909ae] [VpxaMoDvs::DeletePorts] deleting port [124] but not portData file in dvs [6d 4d 35 50 ## ## ## ##-## ## ## ## 82 7e e2 77] 
    YYYY-MM-DDTHH:MM:SSZ verbose vpxa[FFEC8B70] [Originator@6876 sub=MoDvs opID=70b909ae] [VpxaMoDvs::DeletePorts] deleting port [13] but not portData file in dvs [6d 4d 35 50 ## ## ## ##-## ## ## ## 82 7e e2 77] 
    YYYY-MM-DDTHH:MM:SSZ verbose vpxa[FFEC8B70] [Originator@6876 sub=MoDvs opID=70b909ae] [VpxaMoDvs::DeletePorts] deleting port [197] but not portData file in dvs [6d 4d 35 50 ## ## ## ##-## ## ## ## 82 7e e2 77]

Environment

VMware vSphere 8.x 

Cause

  • This issue occurs when using a Distributed Switch due to race condition between the cleanup of unused vDS ports (performed by DvsMonitor) and the assignment of the vDS port to the newly moved VM (by vSphere HA or DRS).
  • This results in the port being deleted before the VM can be connected to it.

Resolution

Workaround:

Perform the following to re-connect the vNIC of an affected VM :

  1. Open edit settings of the VM
  2. Change the network of the vNIC. For example, select a different port group.
  3. Save the change.
  4. Go back to edit settings of the VM
  5. Change the network of the vNIC back to the correct network.
OR
  1. Cold migrate the VM to a different host