VMware Workstation Player course

How to Add a New Virtual Hard Disk in VMware Workstation Player

Learn how to add and configure a new virtual hard disk in VMware Workstation Player, then initialize, format, and use it in Windows or Linux.

A new virtual hard disk adds separate blank storage to an existing virtual machine (VM). VMware Workstation Player stores the disk as a file, or group of files, on the host operating system and presents it to the guest operating system as a physical disk.

This procedure adds a second disk. It does not increase the capacity of an existing system disk. To use the new disk, the guest must detect it, initialize it when required, create a partition, format the partition with a file system, and assign a drive letter or mount point.

Before you add the disk

1. Confirm that the correct VM is selected in the VMware library. Check its name and, when possible, its guest operating system.
2. Shut down the guest completely. Do not rely on a suspended state. Hardware changes may be unavailable or unsafe while the VM is running unless the guest and configuration explicitly support hot-add behavior.
3. Check free space on the host volume that will store the new virtual disk. A growing disk still needs enough eventual host capacity if the guest fills it.
4. Decide whether a backup or snapshot is appropriate. A snapshot can provide a recovery point where supported, but it also consumes storage and is not a replacement for an independent backup.
5. Plan the disk's purpose, size, controller type, storage location, and guest drive letter or mount point.

The host operating system is the operating system running VMware and storing VM files. The guest operating system is the operating system installed inside the VM. A virtual hard disk is a host-side file or set of files that VMware presents to the guest as a disk device.

Open Virtual Machine Settings

With the guest shut down, use this interface path:

Select the virtual machine in the library, then open Player > Manage > Virtual Machine Settings > Hardware > Add.

Virtual Machine Settings is the VMware interface for viewing and changing virtual hardware. On the Hardware tab, select Add to open the New Hardware wizard, which guides you through adding a virtual device.

Select Hard Disk

The wizard can add several hardware types. Select Hard Disk, then continue. Choosing the disk device is required before VMware displays virtual storage and controller options.

Choose a virtual disk controller

A controller is the virtual hardware path through which the guest accesses a disk. Choose a controller that the existing VM hardware and guest operating system support.

IDE — A legacy controller type. It supports up to four IDE devices per VM. Use it mainly when compatibility with existing hardware or an older guest requires it.

SCSI — Generally the recommended choice for a new additional disk when there is no compatibility requirement dictating another option. It supports up to 60 SCSI devices per VM.

SATA — A serial controller option that supports up to 120 SATA devices per VM: four controllers with up to 30 devices per controller.

These limits describe the supported virtual device capacity for each controller type. They do not mean that every guest can use every device configuration. Existing controller assignments, guest drivers, boot requirements, and VM compatibility settings should guide the final choice.

Create a new virtual disk

Choose Create a new virtual disk. This is different from attaching an existing virtual disk file. In this workflow, VMware creates a new host-side disk file or set of files, and the VM presents that storage to the guest as a new physical disk.

If you already have a disk file that you want to attach, use Adding an Existing Virtual Hard Disk instead.

Set the virtual disk capacity

Enter the disk's maximum virtual size based on expected data growth. This is the capacity the guest can eventually see, not necessarily the amount of host storage consumed immediately.

For example, a 100 GB growing disk may initially use much less than 100 GB on the host. As the guest writes data, the host-side disk expands toward its configured maximum. The host must ultimately have enough free space if the guest fills the disk.

Choose disk-space allocation

The allocation setting controls when VMware reserves host storage.

Allocate all disk space now: Reserves the full configured capacity during creation. This can provide more predictable performance because the disk does not need to expand during active use. It requires the complete disk size to be available on the host immediately and is useful for workloads involving frequent large data transfers or sustained writes.

Grow the disk as needed: Starts with lower host storage consumption and expands as the guest writes data, up to the maximum virtual size. This is convenient when the guest will use the space gradually, but host free space must be monitored and expansion can add overhead during active use.

Choose the virtual disk file layout

Next choose how VMware stores the virtual disk on the host.

Single file: Stores the disk as one large host-side file. This is straightforward to organize and can be convenient on modern file systems that support large files.

Split into multiple files: Stores the disk as several host-side files. This can help when the destination file system has a restrictive maximum file size, including older file systems with limits of approximately 2 GB per individual file. Split files can also make some transfers easier.

File layout is a host-side storage decision. It does not change how the guest sees the disk or how the guest creates partitions and file systems. Before selecting a single file, verify that every destination used for storing or moving the VM supports the required file size.

Name and locate the virtual disk

1. Enter a meaningful disk file name, such as AccountingData.vmdk or LinuxArchive.vmdk.
2. Choose a host location with sufficient free space, suitable storage performance, and appropriate backup coverage.
3. Keep disk files organized by VM and purpose. Clear names and consistent locations reduce the risk of modifying, copying, or deleting the wrong disk.
4. Review the summary and complete the wizard.

After completion, the new disk should appear in the VM's Hardware list. Confirm its controller, capacity, and file location before closing Virtual Machine Settings.

Controller and allocation decisions at a glance

IDE | Compatibility-focused legacy controller | Up to 4 devices | Use only when existing hardware or guest support calls for it.

SCSI | Common choice for an additional disk | Up to 60 devices | Generally recommended for a new disk when supported.

SATA | Serial controller option | Up to 120 devices: 4 controllers, 30 devices each | Use when the VM and guest support it.

Allocate all disk space now | Full capacity consumed on host immediately | Predictable storage and potentially steadier performance | Requires all host space at creation | High-write or large-transfer workloads with sufficient host capacity.

Grow as data is written | Host usage expands to the maximum virtual size | Uses less space initially | Requires free-space monitoring and may expand during use | Gradual data growth.

Single file | One large host file | Simple organization | Requires a destination that supports the file size | Modern file systems and stable VM locations.

Split into multiple files | Several host files | Helps with file-size restrictions and some portability needs | More files to manage | Constrained or older destination file systems.

Prepare the disk inside Windows

Start or resume the VM after the hardware change. Windows may detect a new uninitialized disk, but detection alone does not make it usable for normal file storage.

1. Open Disk Management.
2. Find the newly detected blank disk by checking its size and status. Do not select the system disk by mistake.
3. Bring it online if Windows shows it as offline.
4. Initialize the disk if prompted. Select the partition style appropriate for the guest and expected capacity.
5. Create a new volume or partition.
6. Format it with a suitable file system.
7. Assign a drive letter.
8. Open the new drive and write a small test file.

The exact prompts can vary by Windows version. Always verify the disk identity and capacity before applying initialization or formatting because these operations can destroy existing data on a selected disk.

Prepare the disk inside Linux

Linux represents disks as block devices. First identify the new device and compare its size with the capacity configured in VMware.

lsblk
sudo fdisk -l
sudo blkid

After identifying the new device, create the desired partition layout, format the partition, create a mount point, and mount it. The following example uses placeholder device names:

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

For persistent mounting after reboot, add an appropriate entry to /etc/fstab. Prefer the partition UUID reported by blkid rather than relying only on a device name such as /dev/sda1, because device names can change.

Post-change validation

1. Confirm that the guest sees a disk with the expected capacity.
2. Confirm that Windows shows the expected drive letter or Linux shows the expected mounted file system.
3. Write and read a small test file.
4. Check that the guest can still reboot and that the new storage remains available.
5. For a growing disk, monitor free space on the host volume. Guest free space and host free space are separate capacity concerns.
6. Document the disk purpose, controller type, virtual size, allocation behavior, host location, and guest drive letter or mount point.

Troubleshooting

The Add button or hardware settings cannot be changed

The VM may be running or suspended, or the wrong VM may be selected. Shut down the guest fully, reopen Virtual Machine Settings, and confirm the VM name in the library.

The host reports insufficient disk space

The requested virtual capacity may exceed free host storage, especially when allocating all space immediately. Free space, choose a larger destination volume, or reduce the virtual capacity if appropriate. A growing disk is not a solution unless the host can accommodate its eventual maximum size.

The guest does not show the new disk

Verify that the disk appears in the VM Hardware list. Restart the guest or rescan storage devices using the guest's tools. Confirm that the change was made to the intended VM, then check Windows Disk Management or Linux block-device listings.

The disk is visible but cannot store files

The disk is probably blank or unprepared. Complete initialization, partitioning, and formatting. In Windows, assign a drive letter; in Linux, mount the file system at the required path.

A single disk file cannot be copied to the destination

The destination file system may impose a maximum file-size limit. Move the VM to a destination that supports the required size or create the disk using split virtual disk files.

The VM or host slows down as disk usage increases

A growing disk may be expanding while the guest is active, or the host storage device may have limited performance or low free space. Maintain adequate host capacity, use suitable storage, and consider preallocation for predictable high-throughput workloads.

Key exam and administration notes

• Adding a new virtual hard disk creates separate blank storage; it does not enlarge an existing disk.
• The guest must initialize when required, partition, format, and mount or assign a letter before storing normal files.
• SCSI is generally preferred for an additional disk when compatibility permits; IDE supports 4 devices, SCSI 60, and SATA 120.
• A preallocated disk consumes its full host capacity immediately. A growing disk consumes host space as data is written, up to its maximum.
• Single-file and split-file choices affect host storage and portability, not the guest's view of the disk.
• Always verify the target VM, host location, disk size, and device identity before destructive guest-side operations.

For broader context, review Virtual Disks Explained, Virtual Machine Files Overview, and the VMware Workstation Player course.