Connecting a vNIC to a vDS fails with the error: Invalid configuration for device '0'
search cancel

Connecting a vNIC to a vDS fails with the error: Invalid configuration for device '0'


Article ID: 324558


Updated On:


VMware vCenter Server VMware vSphere ESXi


When performing a virtual machine migration using vMotion in a vSphere 5.x environment, you experience these symptoms:
  • Cannot connect a virtual machine's virtual NIC (vNIC) to a vSphere Distributed Switch (vDS) portgroup after performing a vMotion
  • Trying to connect the vNIC to a vDS portgroup after migration to the new ESXi host fails
  • The vMotion migration fails and you see this error in the vSphere Client:

    Invalid configuration for device '0'
  • In the /var/log/ hostd.log file, you see the entries similar to:

    <YYYY-MM-DD>T<time>.783Z [39282B70 verbose 'Hostsvc.NetworkProvider' opID=16d8c9f2-e3 user=vpxuser] DVPort 542 on dvs b0 1a 38 50 b0 05 61 04-2a ad 48 5e 55 ae 51 5a not found
    <YYYY-MM-DD>T<time></time>.783Z [39282B70 error 'Vmsvc.vm:/vmfs/volumes/547e2d16-3f592880-f6ae-0025b3a4b008/VM Folder/VM Name.vmx' opID=16d8c9f2-e3 user=vpxuser] Device spec doesn't match up with dvport/dvpg configuration

    Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.


VMware vCenter Server 6.0.x
VMware vCenter Server 5.1.x
VMware vSphere ESXi 6.0
VMware vSphere ESXi 5.1
VMware vSphere ESXi 5.0
VMware vCenter Server 5.5.x
VMware vCenter Server 5.0.x
VMware vSphere ESXi 5.5


This issue occurs when migrating a virtual machine with a disconnected vNIC, the Connected option is deselected for the vNIC in the virtual machine configuration. vCenter Server does not correctly pass port information to the destination ESXi host during vMotion migration and the vNIC cannot be reconnected to a portgroup on the destination host.


This is a known issue affecting vCenter Server and ESXi 5.0, 5.1, and 5.5.

Currently, there is no resolution for vCenter Server and ESXi 5.0 and 5.1.

This issue is resolved in VMware vCenter Server 5.5 Update 3 and VMware ESXi 5.5 Update 3, available at VMware Downloads.

For more information, see the:
Where upgrading is not possible, work around the issue by migrating the virtual machine back to the original ESXi host, manually connect the virtual NIC to another portgroup and then connect it back to the original vDS portgroup.
To migrate the virtual machine back to the original ESXi host and reconfigure the virtual machine portgroup it is attached to:
  1. Open the vSphere Web Client.
  2. Click Edit Settings > Migrate to migrate the virtual machine back to the ESXi host that originally hosted the virtual machine using vMotion.
  3. Right-click the virtual machine, click Edit Settings, and select the Connected option for the affected vNIC.
  4. Modify the vNIC configuration and connect to a different vDS portgroup, ensure the vNIC is connected.
  5. Modify the vNIC configuration again and set it back to the desired virtual machine vDS portgroup.
To prevent the issue from reoccurring avoid performing vMotion migrations for virtual machines with disconnected virtual NICs. When the Connected option is not selected for the vNIC, the configuration of the disconnected vNIC cannot be migrated correctly.

Note: When the affected vCenter Server virtual machine with the management network is configured on the vDS, you must make vCenter Server available before you can edit the settings as described in the preceding workaround:
  1. Using the vSphere Client connect directly to the host where the vCenter Server virtual machine resides.
  2. Put the host into maintenance mode.
  3. Create a blank standard switch(vSS).
  4. Migrate a physical nic to the vSS.
  5. Migrate a vmk port to the vSS.
  6. Create VM network on the vSS.
  7. Attach vCenter Server virtual machine to this VM network.
  8. Migrate vCenter Server to the management port group on the vDS (assuming link redundancy).
  9. Migrate the physical NIC and vmk port back to the vDS.
  10. Delete the empty vSS.

For more information on this issue caused by host's vNIC, see vCenter Server loses network connection after DRS vMotion when configured with DVS network Port Group (1023181).

Additional Information

This issue may also occur in VMware vCenter Site Recovery Manager (SRM) environments with IP customization configured when the recovery site cluster is using DRS in Fully Automated Mode. The issue occurs under these conditions:
  1. SRM recovers the virtual machine on the Disaster Recovery (DR) site.The virtual machine is powered on.
  2. IP customization is configured for the virtual machine, so the virtual machine's vNIC is disconnected while IP customization is performed.
  3. DRS migrates the virtual machine to a new ESXi host using the fully automated policy.
  4. SRM performs IP customization and attempts to reconnect the vNIC.
  5. The reconnection fails due to this issue.
For affected SRM environments, changing the recovery site DRS configuration to Partially Automated mode in the Cluster Settings prior to performing a Test Failover or a Failover prevents the issue .
vCenter Server loses network connection after DRS vMotion when configured with DVS network Port Group
Enabling a virtual NIC for a virtual machine in a vDS portgroup after a storage migration fails with the error: Invalid configuration for device '0'
Performing a vMotion or cold storage and host migration fails at 99% with the error: Invalid configuration for device
VMware ESXi 5.5, Patch Release ESXi550-201501001
vDS への vNIC の接続が次のエラーで失敗する: デバイス「0」では無効な構成です
将 vNIC 连接到 vDS 失败并显示错误:设备“0”的配置无效 (Invalid configuration for device '0')