How to Add a New Virtual Hard Disk in VMware Player

Learn how to add a blank virtual hard disk to an existing VMware Player VM, choose its interface and storage layout, and prepare it in Windows or Linux.

Adding a new virtual hard disk gives an existing virtual machine an additional blank storage device. VMware Player creates or attaches the disk on the host computer and presents it to the guest operating system as virtual hardware.

The VMware step does not create a usable volume by itself. After the guest detects the disk, you must initialize or partition it, create a filesystem, and mount it or assign it a drive letter. Shut down the virtual machine completely before changing its virtual hardware; do not leave it running or merely suspended.

Before you begin

Confirm that you selected the intended local virtual machine.
Shut down the guest operating system rather than suspending the VM.
Check the host volume's free space, permissions, and file-size limits.
Decide the disk's purpose, maximum capacity, interface type, and host location.
Back up important guest data before performing any disk or partition operation.

Open the virtual machine hardware settings

Open VMware Player and select the target virtual machine in the library.
Open Player > Manage > Virtual Machine Settings. Menu names can vary slightly between VMware Player releases.
Select the Hardware tab.
Click Add to start the new hardware wizard.

Virtual Machine Settings is the VMware Player interface for reviewing and changing the VM's virtual hardware. If the controls are unavailable, verify that the machine is powered off and that the correct VM is selected.

Add a new hard disk

In the New Hardware wizard, select Hard Disk, then continue.
Choose a virtual disk interface type: IDE, SCSI, or SATA.
Choose Create a new virtual disk. Do not choose the option for using an existing virtual disk file unless you already have a disk image to attach.
Set the maximum capacity and choose how the host allocates disk space.
Choose whether to store the disk as one file or split it into multiple files.
Enter a recognizable filename and select a host directory with sufficient capacity and appropriate access permissions.
Finish the wizard.

Creating a new disk produces a host-side virtual disk file. VMware adds that file to the VM configuration and exposes it as a separate, initially blank drive inside the guest.

Choose the disk interface

The interface type identifies the virtual controller through which the disk connects to the guest. It affects guest compatibility, how the device is presented, and the number of devices available. SCSI is the normal general-purpose choice for an additional disk when the guest supports it.

Interface type	Typical use	Maximum device count	Notes
IDE	Legacy compatibility	Up to 4 devices	Use when an older guest requires IDE or does not support another controller.
SCSI	Recommended general-purpose choice	Up to 60 devices	Usually suitable for additional storage when supported by the guest.
SATA	Modern SATA-style attachment	Up to 120 devices	Up to 4 controllers, with 30 devices per controller.

A controller is the virtual hardware component through which one or more disk devices connect to the guest. The maximum counts describe virtual devices, not physical disks installed in the host.

Set capacity and host-space allocation

Set the disk's maximum capacity according to the guest's expected storage needs and the host's available storage. The configured capacity is the largest size the guest can use; it does not remove the need to monitor actual free space on the host.

Option	Host-space behavior	Advantages	Trade-offs	Best fit
Allocate all disk space immediately	Reserves the configured capacity when the disk is created.	Predictable host-space usage and potentially better performance.	Requires the entire capacity to be available immediately.	Workloads needing predictable allocation and hosts with sufficient free space.
Growable or non-preallocated disk	The backing file expands as the guest writes data, up to its maximum size.	Uses less host space initially.	Host space can become exhausted later, and growth may add overhead.	Labs or lightly used disks where host capacity is monitored.
Store as one file	Stores the virtual disk in one host file.	Simple organization and handling on file systems that support large files.	May be difficult to copy or create on a file system with file-size limits.	Normal host storage with adequate large-file support.
Split into multiple files	Stores one virtual disk as several host files.	Useful for file systems or transfer workflows with file-size restrictions.	Creates more files to manage and transfer.	Hosts or workflows that cannot reliably handle one large file.

Preallocation is the act of reserving the disk's configured capacity immediately. A growable disk can still consume the full maximum capacity over time, so check host free space after creating and using it.

Name and store the disk

Use a descriptive filename such as development-data.vmdk rather than an ambiguous name. Store it in a directory associated with the virtual machine or another approved host location. The VM configuration records which virtual disk file is attached; moving or renaming that file outside VMware can make the disk unavailable.

Finish and verify the VMware Player workflow

Complete the wizard and return to the Hardware list.
Confirm that the new hard disk appears with the selected interface and capacity.
Apply or save the hardware change if VMware Player presents an additional confirmation.
Start the virtual machine.
In the guest operating system, confirm that an additional disk is detected and is initially uninitialized or unformatted.

If the disk is not listed in VMware Player, it was not successfully added to the VM configuration. If it is listed there but absent in the guest, restart the guest or rescan its storage devices and check that the selected controller is supported.

Prepare the disk in a Windows guest

Open Disk Management.
Locate the newly detected disk by matching its new capacity and by confirming that it does not contain the existing system or data partitions.
When prompted, initialize the disk and choose a partition style, commonly GPT for modern systems or MBR when compatibility requires it.
Create a new simple volume.
Format the volume with a suitable filesystem such as NTFS.
Assign a drive letter or mount point.
Write a test file and verify that the new volume is visible and writable.

Prepare the disk in a Linux guest

First identify the new block device. Device names such as /dev/sdb and /dev/sdc can change between systems, so do not assume that a particular name is correct. Compare the reported capacity with the disk you added.

lsblk
sudo fdisk -l

The following example creates a GPT partition table, creates one ext4 partition, formats it, and mounts it. Replace /dev/sdX only after positively identifying the new blank disk.

sudo parted /dev/sdX --script mklabel gpt
sudo parted /dev/sdX --script mkpart primary ext4 0% 100%
sudo mkfs.ext4 /dev/sdX1
sudo mkdir -p /mnt/data
sudo mount /dev/sdX1 /mnt/data
sudo blkid /dev/sdX1

Check the mounted volume and test writing to it. For persistent mounting after reboot, use the UUID reported by blkid in an appropriate /etc/fstab entry. Test the entry carefully before rebooting.

Validation and capacity management

Verify that the new Windows volume or Linux mount point is visible and writable.
Check free space in both the guest volume and the host directory containing the virtual disk.
Remember that a guest may report a large virtual capacity even while the host has limited free space.
Document the disk's purpose, capacity, interface type, filename, and host location.
Do not delete a virtual disk file directly while it remains attached to the VM. Remove or detach it through the VM hardware settings first, and confirm that it is not needed.

Troubleshooting

The Add button or hardware settings cannot be changed

Cause: The VM is powered on or suspended.
Fix: Shut down the guest completely, return to the library, confirm the intended VM is selected, and reopen Virtual Machine Settings.

The guest does not show the new disk

Confirm that the disk appears in VMware Player's Hardware list.
Restart the guest or use its storage-rescan function.
Check for a controller-driver or compatibility problem and select a guest-supported type, commonly SCSI for general use.

The disk appears but cannot be used

A newly created disk is blank. Complete initialization, partitioning, filesystem creation, and drive-letter or mount-point assignment in the guest.

The host runs out of disk space

A preallocated disk consumes its configured capacity immediately. A growable disk expands as data is written. Free space on the host, relocate the VM files to a larger host volume, or revise the capacity plan. Do not assume that a growable disk is unlimited.

A single disk file cannot be created or copied

The destination file system may impose a maximum file-size limit. Choose a split virtual disk layout or use a destination file system that supports the required file size.

The wrong disk was selected in the guest

Stop before formatting or partitioning. Match the disk by its newly added capacity, inspect its existing partitions, and back up important data. Similar disk numbers are common in multi-disk VMs.

Related VMware Player tasks

Add an existing virtual hard disk when you already have a disk image file.
Configure a virtual hard disk to review disk attachment settings.
Expand a virtual hard disk when an existing disk needs more capacity.
Learn about virtual machine files before moving or managing host-side disk files.
Add a generic SCSI device for other SCSI hardware requirements.