"Error: A general system error occurred: vDS host error" powering on a virtual machine

Products

• VMware vCenter Server

Issue/Introduction

This article provides information on troubleshooting and fixing the virtual machine (VM) error: A general system error occurred: vDS host error

Powering on a virtual machine (VM) fails with the error:
A general system error occurred: vDS host error

or 

A general system error occurred: vDS host error: see faultCause Cannot create DVPort ### of VDS <DISTRIBUTED SWITCH NAME> on the host <hostname.example.com>

Environment

VMware vCenter Server 7.0.x

VMware vCenter Server 8.0.x

vSphere ESXi 7.x 
vSphere ESXi 8.x

VCF 9.0 

 

Cause

This issue is caused by an incorrect database record for the particular VM virtual network interface card (NIC)

Resolution

To resolve this issue, re-add the virtual NIC to create a clean database record for the VM.

Caution: This procedure is valid ONLY for vSphere-only environments. Re-adding VM virtual NICs can cause unanticipated difficulties when using add-on products such as:

• vRealize Automation
• Horizon View
• vCloud Director
• VMware Integrated Openstack

If you have any uncertainty about whether other products have been added onto vCenter Server, do not follow this procedure.

1. Find the VM object in the vCenter Hosts and Clusters view.
2. Right-click the VM and select Edit Settings...
3. Make note all of the virtual NIC settings.
4. Delete the virtual NIC.

Note: If the VM has more than one virtual NIC, only remove one virtual NIC at a time. If you are using vCloud Director, please see Remove a Network Interface.

5. Save the change.
6. Right-click the VM again and select Edit Settings...
7. Re-add the virtual NIC using the same settings.

If the VM has more than one virtual NIC, and still won't power on, use steps 1-7 for the next virtual NIC.

Note: 

Prior to following steps of removing NIC and adding back, the issue may be resolved by also changing the port group on the VM, power it on and then change it back to original.

**Make sure to take note of the original portgroup assigned to the VM, and change back to this once VM is up and running again. 

Additional Information

Impact/Risks:
Removing, then re-adding, VM virtual NICs should NOT be done when using VMware add-on products such as:

• vRealize Automation
• Horizon View
• vCloud Director
• VMware Integrated Openstack

Failed to power on virtual machine