The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
Virtual machines lose network connectivity after deploying from template, customizing, and powering on after creation using dynamic portbinding (1037675)
- Virtual machines that are deployed from a virtual machine or template via customization and Power on this virtual machine after creation on dynamic binding dvportgroup do not have a network connection after boot-up.
- The hostd log contains entries similar to:
info: Unable to get dvs.portId for ethernet0Unable to get networkName or devName for ethernet0Failed to connect virtual device Ethernet0.
verbose 'vm:/vmfs/volumes/4cdc263f-cb60ef1e-d7ca-842b2b04838a/test100/test100.vmx'] Auto-answered question Unable to get dvs.portId for ethernet0Unable to get networkName or devName for ethernet0Failed to connect virtual device Ethernet0.
- If you deploy Virtual machine with dynamic binding on vNetwork Distributed Switch it does gets mapped with dvportgroup after deployment via customisation is complete.
Template deployment via customization of a virtual machine with dynamic binding on dvPortgroup is not supported. To restore the connectivity, manually edit the virtual machine settings and map it to appropriate dvSwitch.
To manually edit the virtual machine settings and map it to appropriate dvSwitch:
Log into vCenter Server of the ESX host using vSphere Client.
Right-click the deployed virtual machine and choose Edit Settings.
Highlight the network adapter (Network Adapter 1).
Under the Network Connection dropdown, choose the appropriate dvSwitch.
Under device status, ensure that Connected and Connected at power on are selected.
Click OK to apply the changes.
Always use the default port binding (static) while deploying template via customization.
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.