VMware ESXi and vSphere Cluster Management

Add Virtual Hardware to a VMware vSphere Virtual Machine

Learn how to add virtual hardware, especially a network adapter, to an existing VMware vSphere VM and validate hot-add, networking, and guest OS settings.

Overview

A virtual machine (VM) is a software-defined computer hosted by a hypervisor. Its virtual hardware consists of the virtual devices assigned to it, such as network adapters, virtual disks, storage controllers, and USB controllers.

After a VM is deployed, its hardware requirements may change. You might add a second network adapter for an application backend, attach additional storage, connect a USB device, or add a controller required by a workload. VMware vSphere provides an Edit Settings workflow for these changes.

This lesson focuses on adding a virtual network adapter through the vSphere Web Client or an equivalent vSphere management interface. The same general workflow applies to other supported devices, although their fields and power-state requirements differ.

Why Add Virtual Hardware?

Add a second network path for frontend, backend, management, storage, or backup traffic.
Increase storage capacity by adding a virtual hard disk.
Connect a workload to a required virtual controller or peripheral.
Support an application whose resource or device requirements changed after deployment.
Prepare hardware for a future configuration while keeping the existing VM identity and operating system.

Adding a device in vSphere changes the VM's virtual hardware definition. It does not automatically complete the configuration inside the guest operating system. For example, adding a virtual network adapter makes a new NIC available to the guest, but the guest may still need a driver, IP address, subnet, gateway, DNS settings, routes, or VLAN-related configuration.

Hot-Add and VM Power State

Hot-add, also called hot-plug, means adding a supported virtual device without shutting down the running VM. Hot-add can reduce downtime, but it is not available for every device or every VM.

Availability depends on the device type, VM hardware compatibility level, guest operating system support, vSphere version, VM configuration, and environment policies. Permissions and other configuration restrictions can also prevent a change while the VM is powered on.

Devices commonly presented as hot-pluggable may include:

USB controllers
SATA controllers
Ethernet or network adapters
Virtual disks
SCSI devices and, in supported configurations, SCSI-related hardware

These examples do not guarantee that a particular device can be added live in your environment. Before editing a running VM, check the device's hot-add support and whether the VM's compatibility and guest configuration meet the requirements. If support is unavailable or uncertain, schedule a maintenance window and power off the VM before changing its hardware.

Open the VM Hardware Settings

Open the vSphere Web Client or your equivalent vSphere management interface.
Use the vSphere Inventory to locate the target VM. Inventory is the organizational view used to find managed hosts, VMs, networks, and other objects.
Open the VM context menu or actions menu.
Choose Edit Settings. This is the VM configuration page used to add, remove, and modify virtual devices.
Check the VM power state and confirm that the planned change is supported while the VM is running. Power off the VM if the device or configuration requires it.

Add a Virtual Network Adapter

1. Add the device

In the VM settings page, locate the New device control.
Select Network or Network adapter, depending on the interface version.
Choose Add or the equivalent control. The new network device appears in the VM hardware list.
Expand the new network adapter section to expose its configurable properties.

2. Configure the adapter

A network adapter is a virtual NIC that provides network connectivity to the guest. Review the following fields:

Adapter type: Select a virtual NIC model supported by the guest operating system and appropriate for the VM's compatibility and performance requirements.
Network or port group: Select the destination network. A port group is a virtual networking connection point that associates a VM NIC with a vSwitch or distributed switch network.
Connected: Enable this when the adapter should be attached to the selected virtual network now.
Connect at power on: Enable this when the adapter should automatically attach whenever the VM starts.

3. Review and save

Review the pending hardware list and confirm that the new NIC has the intended adapter type and network assignment.
Confirm the connected state and connection-at-power-on behavior.
Check any warning about hot-add, compatibility, permissions, or required shutdown.
Save, apply, or confirm the VM settings.

After the configuration is saved, confirm that the added NIC remains visible in the VM hardware inventory. If the VM is running and hot-add is supported, the device may become available without a restart. Otherwise, start the VM after the required maintenance action.

Example: Add a Second NIC for a Backend Network

Suppose a web or application VM already uses one NIC for its primary network and needs a separate path to a backend network.

Open the VM's Edit Settings page while the VM is running or powered off, after confirming whether network-adapter hot-add is supported.
Use New device and add a Network device.
Assign the new adapter to the backend port group.
Choose a NIC type supported by the guest operating system.
Enable Connected if the interface should be available immediately.
Enable Connect at power on if the interface must persist across VM reboots.
Save the settings.
Inside the guest, detect the new interface and configure its addressing, routes, and any required policy.
Test connectivity to the backend network without disrupting the existing interface.

The result is a VM with separate virtual network paths for its existing traffic and the backend workload network.

Network Adapter Configuration Checklist

Setting	Why it matters	Example decision
Adapter type	Determines the virtual NIC model exposed to the guest and must match guest support and compatibility requirements.	Use a guest-supported model recommended for the VM environment.
Port group or network	Determines which virtual network receives the VM's traffic.	Select the backend port group for a backend application interface.
Connected state	Controls whether the virtual NIC is attached to the selected network.	Enable it when the interface should be usable immediately.
Connect at power on	Controls whether the adapter reconnects automatically after startup.	Enable it for an interface that must be present after every reboot.
Guest OS driver and IP configuration	The guest must recognize the device and have valid network settings.	Install or verify the driver, then configure DHCP or a planned static address.

Post-Add Validation

In vSphere, confirm that the added NIC appears in the VM hardware inventory.
Verify the selected port group or network.
Verify the adapter's connected state and connection-at-power-on setting.
Inside the guest operating system, inspect the network interface list.
Install or verify the required guest driver if the adapter is not detected.
Configure DHCP or static addressing according to the network design.
Check the subnet mask or prefix, default gateway, DNS servers, and routes as applicable.
Where VLAN-related settings are part of the design, verify the port group and virtual-switch configuration with the virtualization or network team. Do not assume that changing a guest IP setting alone changes the VLAN.
Test local interface status, gateway reachability, DNS resolution, and access to the intended application or service.

Adding Other Virtual Devices

The same vSphere settings workflow can be used for other supported hardware:

Locate the VM in inventory.
Open Edit Settings.
Use New device to select the required hardware.
Configure the device-specific fields.
Review power-state warnings and compatibility requirements.
Save the configuration and complete any guest-side setup.

Device-specific requirements differ. A virtual hard disk requires datastore, capacity, controller, provisioning, and disk-mode decisions. A SCSI controller is a virtual controller used to connect virtual disks and certain storage-related devices. A SATA controller is a virtual storage controller available when supported by the VM configuration. USB devices may require host or passthrough considerations. Some changes require the VM to be powered off even when another device type supports hot-add.

Common Virtual Hardware Additions and Planning Considerations

Virtual device	Typical use	Potential hot-add availability	Key settings to review	Guest OS follow-up
Network adapter	Add a network path or separate traffic types.	Often supported, subject to VM, guest, and environment requirements.	Adapter type, port group, connected state, and connect at power on.	Detect the NIC, install a driver if needed, and configure addressing and routes.
Virtual hard disk	Increase storage capacity or provide a separate data volume.	Often possible for supported configurations, but device and controller rules apply.	Datastore, size, provisioning, controller, and disk mode.	Rescan storage, initialize or format the disk, and mount it as required.
SCSI device or controller	Connect virtual disks and supported storage-related devices.	Depends on the controller, device, VM, and guest configuration.	Controller type, bus or unit number, and device compatibility.	Rescan storage and verify the guest driver and device mapping.
SATA controller	Provide a virtual SATA connection for supported devices.	Available only when supported by the VM and environment.	Controller allocation and attached devices.	Verify guest controller recognition and attached-device visibility.
USB controller	Support USB devices or workloads that require USB connectivity.	May be hot-pluggable, but host, passthrough, and guest support affect availability.	Controller version, host connection, and passthrough or attachment settings.	Verify the guest detects the controller and required USB device.

Troubleshooting

Hardware cannot be added while the VM is running

Likely causes: The selected device does not support hot-add in the current configuration, the VM compatibility level or guest support is insufficient, or your permissions do not allow VM hardware modification.

Resolution: Review the device and guest requirements, power off the VM if necessary, and confirm that your administrator role includes the required VM configuration privileges.

The new NIC does not appear in the guest

Likely causes: The adapter is disconnected, the selected NIC model lacks a usable guest driver, or the guest has not refreshed its hardware inventory.

Resolution: Check the adapter's connected setting in vSphere, select a guest-supported adapter type, install the appropriate driver, and rescan devices or restart the guest when necessary.

The NIC is visible but cannot communicate

Likely causes: The wrong port group was selected, guest IP, subnet, gateway, or DNS settings are incorrect, or the target network has VLAN, security, or uplink restrictions.

Resolution: Verify the NIC's assigned port group, validate guest addressing and routing, and check virtual-switch, VLAN, and physical-network configuration with the network team.

The NIC disconnects after a reboot

Likely cause: Connect at power on was not enabled.

Resolution: Edit the VM settings, expand the adapter, enable the startup connection option, and save the configuration.

Exam-Relevant Notes

Hot-add means adding supported virtual hardware without shutting down the running VM; it is conditional, not universal.
Edit Settings is the vSphere workflow for adding, removing, and modifying VM hardware.
A port group determines which virtual network a VM NIC connects to.
Connect at power on controls whether a device is automatically attached when the VM starts.
Adding a virtual NIC in vSphere does not configure the guest OS. Driver, IP, routing, DNS, and connectivity work may still be required.
Always verify the device, VM compatibility level, guest support, permissions, and required power state before making a hardware change.

For related procedures, see Add virtual hardware to a VM.