Search the VMware Knowledge Base (KB)
View by Article ID

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' (2014469)

  • 37 Ratings


After you perform a storage migration using storage migration on a virtual machine, you experience these symptoms:
  • A virtual machine that is part of a vDS PortGroup is disconnected from the network.
  • Attempting to enable a virtual NIC for a virtual machine by selecting Connected in Edit Settings in vCenter Server fails with the error:

    Invalid configuration for device '0'
Note: This article describes a specific issue. If you experience all of preceding symptoms, read other sections in the article. If you experience some but not all of these symptoms, your issue is not related to this article. Search for your symptoms in the Knowledge Base or Open a Support Request.


This issue occurs when a host is abruptly turned off or power-cycled following a storage migration task using storage migration and this results in a discrepancy in the cached Distributed vSwitch configuration file on a VMFS volume.


This is a known issue affecting ESXi 5.0 and ESXi 5.1.

This issue is resolved in ESXi 5.0 Update 2, available at VMware Downloads. For more information, see the VMware ESXi 5.0 Update 2 Release Notes.

Currently, there is no resolution for this issue in ESXi 5.1.

To work around this issue, restart the management agents on the ESXi/ESX host where the virtual machine is registered. For details, see  Restarting the Management agents on an ESXi or ESX host (1003490).

If the issue persists, complete one of these workarounds:

Note: These workarounds assume that vCenter Server is available. If the database resides on a separate virtual machine/physical machine, these workarounds also assume that the vCenter Server database is available.

    Option 1

    1. Verify which dvPort is unused in a vDS PortGroup:

      1. In vCenter Server, click Home > Networking.
      2. Expand the vDS and locate the affected dvPortGroup.
      3. Click the appropriate dvPortGroup tab.
      4. In the list of ports, determine which dvPortGroup does not have a virtual machine or VMkernel port name in the Connected column.

    2. Click Edit Settings in the affected virtual machine.
    3. Go to Virtual NIC > Advanced > Change the dvPort to an unused dvPort.
    4. After the reconfiguration is complete, select Connected for the virtual NIC on the virtual machine.
    5. Verify that connectivity from the virtual machine is restored.

    Option 2

    1. Click Edit Settings in the affected virtual machine and disconnect the vNIC.

      Note: In a Linux virtual machine, reconfiguration of the ethernet config file may be required if the guest does not support hot add/remove.

    2. Migrate the affected virtual machine to another host using vMotion or cold migration.
    3. Reconnect the vNIC after the vMotion operation has successfully completed.

    Option 3

    1. SSH to the host and determine the VMID for the affected virtual machine using the command:

      vim-cmd vmsvc/getallvms | grep -i VMNAME

    2. Use the VMID from the command in step 1 to reload the configuration on the host by running the command:

      vim-cmd vmsvc/reload VMID

    3. Edit the settings of the virtual machine and connect the NIC.

    Option 4

    Replace the vNIC on the virtual machine:

    1. Obtain the correct network information for the vNIC, such as Static IP, Subnet Mask, VLAN, and the dvPortGroup information.
    2. Shut down the guest virtual machine that reports the error.
    3. Remove the vNIC.
    4. Add a new vNIC and populate it with the information noted in step 1, such as Static IP, Subnet Mask, and VLAN.
    5. Select the dvPortGroup noted in step 1.
    6. Clear the alarm from vCenter Server.
    7. Using the console, verify the network information from the guest operating system.

Additional Information

To be alerted when this article is updated, click Subscribe to Document in the Actions box.



See Also

Update History

11/10/2012 - Added Option 4 to Resolution 11/19/2012 - Added ESXi 5.1 to Products 12/17/2012 - Added note on the assumption that vCenter Server is available 07/06/2013 - Added resolution information 01/30/2015 - Added link to KB 1003490 in workaround

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.


  • 37 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)

Please enter the Captcha code before clicking Submit.
  • 37 Ratings