When attempting to clone a virtual machine (VM) using vSphere Client, the operation may fail if any virtual disks in the source VM are larger than the available space in the target datastore, even if those disks are not intended to be part of the final cloned VM.
- VMware vSphere 6.x and later
- vCenter Server
- ESXi hosts
- The "Clone to Virtual Machine" wizard prevents proceeding at the storage selection step
- Error message "Select a valid destination storage" appears
- Unable to reach the disk customization step where unwanted disks could be removed
The vSphere cloning process validates available storage space before allowing disk customization. This validation checks space requirements for all virtual disks, regardless of whether they will be included in the final clone.
Two methods are available to work around this limitation:
Method 1: ESXi Command Line (No VM Downtime Required)
esxcli storage filesystem list
Method 2: vCenter Server UI (Requires VM Downtime)
- Method 1 requires SSH access and command line experience
- Method 2 requires planned downtime
- As a rough rule of thumb, estimate maintenance window duration based on the time it takes to backup the disks being copied
- Double estimated time to account for complications
- Consider testing process on non-production VM first