VMware ESXi and vSphere Cluster Management

Add Virtual Hardware to a Virtual Machine in VMware ESXi and vSphere

Learn how to add a virtual network adapter and other hardware to an existing VMware ESXi or vSphere VM, including hot-add planning, port groups, guest configuration, and validation.

Virtual hardware is the set of virtualized devices presented by VMware to a guest operating system. It includes processors, memory, disks, controllers, and network adapters. After creating a virtual machine (VM), an administrator can use the vSphere Client to add supported devices or change existing hardware settings.

This lesson focuses on adding an Ethernet network adapter to an existing VM. The same Edit Settings workflow can also be used for devices such as virtual disks, SCSI controllers, SATA controllers, and USB controllers. For background navigation, see VMware ESXi and the VMware ESXi online course.

What You Should Plan Before Changing Hardware

Before editing a VM, confirm the correct inventory object, its current power state, and the purpose of the new device. For a network adapter, identify the destination network before opening the settings dialog.

Confirm the VM name, host or cluster, and current power state.
Identify the required port group or distributed port group.
Verify the associated standard switch (vSS) or distributed switch (vDS), VLAN, uplinks, and network policies.
Confirm that your account can modify VM hardware and assign the required network.
For production systems, follow change control and consider a backup or a recorded copy of the current VM configuration.

A port group is a VMware networking object that connects VM adapters to a virtual switch and commonly defines VLAN and port-level policies. A standard switch is configured independently on each ESXi host, whereas a distributed switch is centrally managed across hosts. Selecting the wrong port group can connect a server to a production, management, storage, or isolated network unintentionally.

Hot-Add Versus Powered-Off Changes

Hot-add, also called hot-plug, means adding supported virtual hardware while the VM remains powered on. Some network adapters and other devices can be added this way, but support is not universal.

Whether a device can be added while running depends on the device type, VM virtual hardware compatibility, guest operating system support, VMware configuration, and sometimes the selected controller or adapter model. The vSphere Client may disable the control or reject the task when a requested change is not supported.

Check hot-plug eligibility for the specific VM and device before making a production change. If the platform does not permit the modification while the VM is running, schedule downtime, power off the VM, make the change, and power it on again.

Virtual device	Can it be added while powered on?	Key dependencies or caveats	Post-addition work
Network adapter	Often supported, but not guaranteed	Depends on VM compatibility, guest support, VMware settings, and adapter type	Detect the NIC and configure guest networking
Virtual disk	Often supported	Controller, guest support, disk format, and storage permissions matter	Rescan storage, partition, format, and mount the disk
SCSI controller	Depends on configuration	Controller type and guest driver support can restrict hot-add	Rescan the guest and attach or configure disks
SATA controller	Usually more restricted	VM compatibility and guest support must be checked	Confirm controller and attached devices in the guest
USB controller	Depends on VM and host configuration	USB device availability and passthrough rules may apply	Check guest USB detection and device drivers

Open the VM Hardware Settings

Launch the applicable browser-based vSphere Client or vSphere Web Client.
Locate the VM in the inventory.
Open the VM context menu or Actions menu.
Select Edit Settings.

The exact menu labels can differ slightly between vSphere Client versions. The goal is to open the VM configuration workflow used to modify virtual hardware and VM options.

Add a Virtual Network Adapter

In the Edit Settings window, locate the New Device control.
Select Network Adapter or Network, depending on the client version.
Click the control to add the device. A new network adapter section should appear in the hardware list.
Expand or select the new adapter and review every setting before saving.

Adding the device to the pending hardware list does not finish the task. The adapter must be attached to the intended virtual network, its connection behavior must be reviewed, and the complete configuration must be confirmed.

Configure the New Adapter

Setting	Purpose	Typical choice	Potential issue if incorrect
Network or port group	Connects the adapter to a virtual switch network	The port group for the application, backup, or other intended network	The VM reaches the wrong VLAN or remains isolated
Adapter type	Selects the virtual NIC model exposed to the guest	VMXNET 3 when the guest has suitable driver support; otherwise a supported alternative such as E1000E	The guest may lack a driver or performance may not match requirements
Connected state	Determines whether the virtual link is currently connected	Enabled when the interface should be usable immediately	The guest sees an interface without an active link
Connect at power on	Reconnects the virtual device when the VM starts	Enabled for a persistent interface	Connectivity disappears after a reboot
MAC address mode	Controls how the adapter receives its Layer 2 address	Automatic VMware assignment unless a documented requirement exists	A duplicate or incorrect static MAC can cause conflicts or policy failures

Choose the required network or distributed port group. Confirm its VLAN and switch configuration with the network design. If the client exposes adapter controls, MAC assignment, bandwidth, resource settings, or port-level policies, review them against the application requirements. Avoid manually assigning a MAC address unless the design specifically requires it and the address is guaranteed to be unique.

VMXNET 3 is a VMware paravirtualized NIC intended for high performance. It requires suitable guest operating system driver support. The guest operating system will see the new adapter as an additional network interface; adding it in vSphere does not automatically assign an IP address, route, DNS configuration, or firewall policy.

Save and Apply the Change

Review the pending hardware list and confirm the adapter count, network, adapter type, connection state, and MAC setting.
Click the confirmation or save control in the Edit Settings window.
Wait for the VM reconfiguration task to complete.
Use Recent Tasks or Recent Events to confirm that the reconfiguration succeeded.

For a supported hot-add on a running VM, the virtual NIC can become available without powering off the VM. For a stopped VM, the adapter is normally available when the VM next powers on. If the task fails, do not assume that a partially displayed device is usable; inspect the task error and the final VM hardware inventory.

Post-Addition Validation

Layer	Validation action	Expected result
vSphere hardware inventory	Review the VM hardware list	The new network adapter is present
Virtual switch or port group	Check the adapter's assigned network and connection state	It is connected to the intended port group and VLAN
Guest OS device detection	Open the guest device manager or list network interfaces	A new supported interface is detected
Guest IP configuration	Assign DHCP or static addressing, prefix or subnet, gateway, DNS, and routes as required	The interface has configuration appropriate to its network
Network connectivity	Test reachability to expected hosts and services	Traffic follows the intended network and policy path

Successful link status only proves that the virtual adapter is connected at the virtual network layer. It does not prove that the guest has a correct IP address, route, DNS configuration, firewall rule, or application binding.

Practical Example: Add a Second NIC to a Running Application Server

Confirm that the correct application-server VM is running and that the new interface is approved.
Open the VM's Edit Settings workflow.
Add a Network Adapter through New Device.
Attach it to the application-network port group.
Select a supported NIC model, enable Connected, and enable Connect at power on if the interface must persist after reboot.
Save the change and confirm the completed reconfiguration task.
In the guest, detect the additional interface, assign its IP configuration, and test reachability from the application network.

Practical Example: Add a NIC for an Isolated Backup Network

Identify the backup VLAN-backed port group and verify that it does not provide unintended access to production or management networks.
Add a network adapter and attach it only to that port group.
Enable the connection settings required by the backup schedule.
Configure the guest interface with the backup address and routes.
Do not add a default route through the backup interface unless the network design explicitly requires it.
Test communication with backup infrastructure and confirm that normal application traffic uses the intended interface.

When Hot-Plug Is Unavailable

Schedule an approved maintenance window.
Verify that services have been stopped or protected as required.
Power off the VM.
Open Edit Settings, add and configure the requested device, and save the changes.
Power on the VM and confirm hardware detection and guest configuration.

Not every hardware modification is supported on a powered-on VM. A powered-off change is the normal fallback when the device, VM compatibility level, guest operating system, controller, or VMware configuration does not support hot-add.

Troubleshooting

The device cannot be added while the VM is running

Check whether the selected device and VM compatibility level support hot-add.
Verify that the user has VM configuration privileges and permission to use the target network.
Check whether the VM is in a state that prevents reconfiguration.
Power off the VM if required, then retry the change and inspect the task error details.

The NIC appears in vSphere but not in the guest

Check the guest device manager or network-interface list.
Rescan hardware or reboot the guest if its operating system requires it.
Install or update VMware Tools and applicable guest drivers.
Use a guest-supported adapter model, such as VMXNET 3 where the appropriate driver is available.

The guest sees the NIC but cannot communicate

Confirm that Connected is enabled in VM settings.
Verify the selected port group, VLAN, virtual switch, distributed-switch policy, and uplink connectivity.
Validate the guest IP address, prefix or subnet, gateway, routes, DNS, firewall, and application bindings.
Check upstream network policies and whether the destination service permits traffic from the new address.

Connectivity stops after a restart

Enable Connect at power on for the adapter.
Make the guest interface configuration persistent rather than temporary.

The wrong network is reachable through the adapter

Correct the port group assignment if the wrong VLAN was selected.
Review guest interface metrics, static routes, and default gateway placement.
Check whether firewall, licensing, clustering, or security software treats the new interface differently.

Safe Operational Practices

Use change-control procedures for production VMs.
Document the adapter's purpose, port group, VLAN, MAC address, guest interface name, and IP configuration.
Never attach a NIC to a sensitive network without verifying the VLAN and policy path.
Avoid duplicate static MAC addresses.
Consider application behavior before adding interfaces to systems with strict firewall, routing, licensing, clustering, or security requirements.
After the change, record the completed task and validation results.

Exam-Relevant Notes

Edit Settings is the VM workflow for modifying virtual hardware and VM options.
Hot-add is conditional; a powered-on VM is not automatically eligible for every hardware change.
A network adapter connects to a VMware port group, which carries the relevant virtual-switch and often VLAN configuration.
VMXNET 3 requires suitable guest driver support.
Connected and Connect at power on are separate settings: one controls the current link state, while the other controls startup behavior.
Adding a NIC in vSphere does not complete guest network configuration.

For related administration tasks, see Assign Permissions, Basic ESXi Configuration, Add an ESXi Host to vCenter Server Inventory, and Add a Raw LUN.