VMware ESXi and vSphere Cluster Management

How to Add a New Virtual Hard Disk in VMware Player

Learn how to create and attach a blank virtual hard disk in VMware Player, choose a controller and allocation method, then configure it in Windows or Linux.

What adding a virtual hard disk does

Adding a virtual hard disk gives the selected virtual machine an additional storage device. VMware Player stores the device as one or more files on the host system, the physical computer running VMware Player, and presents it to the guest operating system as a disk.

A newly created disk is blank. After VMware Player attaches it, the guest must usually initialize it, create a partition, create a filesystem, and make the storage accessible. Windows normally assigns a drive letter, while Linux makes a filesystem available through a mount point.

This procedure adds a second disk. It does not increase the capacity of an existing virtual disk. Expanding an existing disk is a different operation that also requires guest-side partition or filesystem changes.

Plan the change first

  1. Select the correct virtual machine in the VMware Player library. Check its name and, if necessary, its guest operating system before changing hardware.
  2. Shut down the guest completely. Do not rely on suspension. Hot-add behavior depends on the guest and VMware configuration, so power-off is the safest general procedure.
  3. Check free space on the host. Consider the maximum virtual disk size, existing virtual machine files, snapshots, and expected future growth.
  4. Decide what the disk is for: application data, operating system data, test workloads, or another purpose. This affects capacity, filesystem choice, performance expectations, and backup planning.
  5. Use an appropriate backup or snapshot plan before making the change. Snapshots are not a replacement for independent backups.

Open Virtual Machine Settings

  1. In the VMware Player library, select the target virtual machine.
  2. Choose Player > Manage > Virtual Machine Settings.
  3. Open the Hardware tab and review the devices already attached. Existing disks and controllers count toward device limits.
  4. Choose Add to open the New Hardware wizard, VMware Player's guided workflow for adding virtual hardware.

Choose the hard disk device

In the New Hardware wizard, select Hard Disk. This tells VMware Player to create and attach a storage device to the current virtual machine. Do not choose an unrelated device such as a network adapter or CD/DVD drive.

Select a virtual disk controller

The controller type determines how the virtual machine connects to the disk. Compatibility with the guest operating system matters more than choosing a particular label.

IDE — A legacy controller type with up to four IDE devices per virtual machine. It can be useful for compatibility with older guests, but it has the smallest device limit.

SCSI — A commonly used controller for additional disks. It supports up to 60 SCSI devices per virtual machine and is generally the recommended choice for a new disk when the guest supports it.

SATA — A broadly compatible controller type supporting up to 120 devices. The limit is four SATA controllers with up to 30 devices per controller.

Account for devices already attached when evaluating these limits. Review the Hardware tab rather than assuming every controller is empty. If the guest does not support the selected controller, choose a compatible option instead.

Create a new virtual disk

Choose Create a new virtual disk. This creates a new blank virtual disk file and adds it to the virtual machine configuration.

The alternative, Use an existing virtual disk, attaches a disk image that already exists on the host. That option is appropriate when reusing or moving a disk, not when you need a new empty disk.

Set capacity and allocation

Enter the disk's maximum capacity. Choose a size based on the guest's expected data, available host storage, and the need for future growth. The guest will see the configured capacity even if the host initially stores only part of it.

Allocate all disk space now: Reserves the full configured capacity on the host during creation. Preallocation can provide more predictable storage behavior and may improve performance by avoiding later file growth, but the entire amount must be available immediately.

Do not allocate all disk space now: Creates a growing virtual disk. Host storage is consumed as the guest writes data, up to the configured maximum. This uses less space at first, but requires ongoing monitoring of host free space.

Single file: Stores the virtual disk as one primary host file or file set. Prefer this when the host filesystem supports the required file size and the disk does not need to be divided for operational reasons.

Split into multiple files: Stores the disk in several files. This can help when the destination filesystem has file-size limits or when splitting makes movement between storage systems easier. It can add file-management complexity.

Choose the layout with the host filesystem, backup tools, and disk-transfer workflow in mind. A single file is not automatically better if the destination cannot reliably store a large file.

Name and place the virtual disk

  1. Enter a meaningful filename, such as dev-data.vmdk. A descriptive name helps identify the disk's purpose.
  2. Select a host location with adequate free space and suitable performance. Fast local storage is usually preferable for active workloads.
  3. Confirm that the selected folder is appropriate for the virtual machine's permissions and backup policy.
  4. Finish the wizard. VMware Player creates the virtual disk files at the chosen location and attaches the new disk to the virtual machine configuration.

The filename and location describe the host-side representation of the virtual hard disk. Do not rename, move, or delete its files manually while the virtual machine is using them unless you are following a supported disk-management procedure.

Start the guest and verify the disk

Start or restart the virtual machine. Confirm that the guest detects one additional blank disk and that the existing system disk remains unchanged.

Windows: Open Disk Management. Identify the new disk by its capacity and blank or uninitialized status. Initialize it, create a new simple volume, format the volume with the required filesystem, and assign a drive letter. Verify that the new drive appears in File Explorer and accepts a test file.

Linux: Identify the disk, create a partition, create a filesystem, mount it, and optionally configure a persistent mount. Verify the mounted path and test read/write access.

Linux example

First inspect disks and partitions. Compare the new disk's size and existing partition list before using a destructive command.

lsblk
sudo fdisk -l

In this example, replace /dev/sdX with the confirmed new disk. Never copy the placeholder literally, and never select the system disk by mistake.

sudo fdisk /dev/sdX
sudo mkfs.ext4 /dev/sdX1
sudo mkdir -p /mnt/data
sudo mount /dev/sdX1 /mnt/data

Check the result with lsblk or a suitable filesystem and mount command. To make the mount persistent after reboot, obtain the filesystem UUID and edit /etc/fstab carefully.

sudo blkid /dev/sdX1
sudoedit /etc/fstab

Use the UUID in the configuration rather than relying only on a device name when appropriate, then test the configuration before rebooting.

Capacity and safety considerations

  • A virtual disk can become unusable, or the guest can report write errors, when the host runs out of physical storage.
  • Monitor host free space, especially for dynamically growing disks and virtual machines with snapshots.
  • Keep backups appropriate to the importance of the guest data. A snapshot can help with short-term rollback but can also consume host storage.
  • Deleting virtual disk files from the host can permanently delete guest data. Remove a disk through the virtual machine's storage configuration only after confirming that its data is no longer needed.
  • Before formatting or partitioning in the guest, verify the disk identifier, capacity, model, and existing partitions.

Troubleshooting

The Add option or hardware settings are unavailable

Ensure the guest is shut down completely rather than running or suspended. Return to Player > Manage > Virtual Machine Settings and try again. If the problem continues, check ownership and permissions for the virtual machine folder and confirm that the selected configuration can be edited.

The guest does not see the new disk

Confirm that the disk appears in the VMware Player Hardware tab and that the wizard was completed. Restart the guest or run its storage-rescan procedure. If the selected controller is unsupported, use a compatible controller, commonly SCSI when the guest permits it.

The host does not have enough space

Preallocation requires the complete configured capacity immediately. A dynamically growing disk may also have consumed available space over time. Free host storage, choose another suitable location, or reduce the planned capacity. Avoid continuing guest writes until the host has adequate free space.

The disk cannot be created as one file

The destination filesystem may impose a maximum file size smaller than the requested disk. Choose the split-disk layout or move the virtual machine to a filesystem that supports the required file size.

The wrong disk was selected in the guest

Stop before partitioning or formatting. Compare capacity, model, device name, and existing partitions using Linux disk tools or Windows Disk Management. A wrong selection can destroy existing data.

A controller device limit has been reached

Review existing hardware and controller assignments. Choose another supported controller or controller location when VMware Player and the guest support it. Remember the limits: four IDE devices, 60 SCSI devices, or 120 SATA devices across four SATA controllers with 30 devices each.

Exam-relevant notes

  • A virtual hard disk is file-backed storage presented to the guest as hardware.
  • The host stores the disk files; the guest initializes, partitions, formats, and mounts the blank disk.
  • Adding a disk is different from expanding an existing disk.
  • Preallocation reserves the full capacity immediately; dynamic allocation grows as data is written.
  • SCSI is generally recommended for a newly added disk when guest compatibility permits.
  • Controller limits include four IDE devices, 60 SCSI devices, and 120 SATA devices using four controllers with 30 devices each.
  • Host free space remains a safety requirement even when the virtual disk is not preallocated.

For related storage procedures, see adding a new virtual hard disk and apply the same host-versus-guest distinction when planning later disk changes.