A VMware VM clone is the process of creating a new virtual machine by copying the configuration and virtual disks of an existing one. The short answer is this: choose the source VM, define the clone type and target compute, validate datastore and network mapping, apply guest customization if needed, and then verify identity, IP, and service health after first boot. This guide is written for teams operating in the September 15, 2025 context.
Quick Summary
- VMware cloning is useful when you want to duplicate the current state of an existing VM quickly, rather than deploy from a strict template workflow.
- Broadcom KB 420149 says that when you clone a powered-on VM, ESXi creates a temporary snapshot and briefly stuns the VM during consolidation. The KB also says this effect is worse under high disk I/O.
- Broadcom KB 409099 shows that clone workflows can fail if the user lacks the
Resource Assign virtual machine to resource poolprivilege. - Broadcom KB 344959 says cross-vCenter clone and migration workflows should use source and destination vCenters on the same version, and when the GUI is used, both vCenters must be in Enhanced Linked Mode within the same SSO domain.
- The same KB 344959 also lists 443 / 8000 / 902 port requirements and says Distributed Switch -> Standard Switch is not supported for networking migration.
- Broadcom KB 380651 explains that the clone wizard validates storage space for all source disks before disk customization, so even disks that will not be included in the final clone can block the process.
- Broadcom KB 321231 says the maximum supported VMDK size on VMFS-5 is 62 TB, and disks larger than 2 TB can only be cloned to compatible hosts and datastore formats.
- In the September 15, 2025 context, Broadcom KB 326316 lists vCenter Server 8.0 Update 3g / 8.0.3.00600 / Build 24853646 as one visible current vCenter 8 baseline.
Table of Contents
- What Exactly Is a VM Clone?
- Which vCenter Baseline Makes Sense on September 15, 2025?
- What Is the Difference Between Cold Clone and Hot Clone?
- How Do You Clone a VMware VM?
- What Should You Check for Cross-vCenter Clone?
- Most Common Clone Errors and Fixes
- First 20-Minute Checklist
- Frequently Asked Questions
Image: Wikimedia Commons - Network Cat6 Patch Rear 1.
What Exactly Is a VM Clone?
A VM clone is a new virtual machine created from the current state of another VM. Operationally, it is useful when you want to duplicate a known working system quickly without going through a full template lifecycle.
Typical use cases include:
- rapidly duplicating similar application servers
- creating test or UAT workloads based on production-like systems
- building temporary migration or backup instances
- branching an existing VM into a separate scenario
This is different from a template workflow. A template is a controlled golden image for repeated deployment. A clone is often a fast copy of a VM as it exists right now.
Related guide:
Which vCenter Baseline Makes Sense on September 15, 2025?
Clone workflows, especially across vCenters, should still be considered in the context of the vCenter management baseline. According to Broadcom KB 326316, one visible vCenter 8 baseline in the September 15, 2025 context is:
- Product: vCenter Server 8.0 Update 3g
- Version: 8.0.3.00600
- Release date: 2025-07-29
- Build: 24853646
This guide uses vCenter Server 8.0 Update 3g / Build 24853646 as the management baseline.
What Is the Difference Between Cold Clone and Hot Clone?
The most important difference is whether the source VM is powered off or powered on.
Cold Clone
A cold clone is taken while the source VM is powered off. It is usually the safer operational choice because application I/O is inactive, there is no snapshot consolidation stun, and data consistency is easier to reason about.
Hot Clone
A hot clone is taken while the source VM is powered on. Broadcom KB 420149 explains that ESXi creates a temporary snapshot for the operation and later consolidates it. During that consolidation, the VM is briefly stunned. The same KB says the stun can last longer when the source VM is under heavy disk I/O.
The practical rule is simple:
- prefer cold clone for critical production workloads
- if hot clone is required, schedule it during low-I/O periods
- treat snapshot consolidation as part of the operational impact window
How Do You Clone a VMware VM?
1. Evaluate the Source VM First
Before cloning, confirm that the source VM is actually suitable to copy. A VM with temporary data disks, user-specific settings, or unstable services is a poor cloning source.
Check:
- hostname and IP behavior
- attached extra disks
- NIC mapping
- application service state
- whether guest customization is required
2. Start the Clone Workflow
In vSphere Client, launch the clone wizard from the source VM and define the new VM name and folder placement. If the result will become a long-lived workload, follow the naming standard from the start.
Related setup flow:
3. Choose the Target Compute Correctly
A clone is not just a disk copy. The target host, cluster, or resource pool matters. Broadcom KB 409099 shows that clone workflows can fail simply because the required privilege is missing.
In particular, verify:
Resource Assign virtual machine to resource pool
Without that privilege, the wizard may fail when selecting the destination compute resource.
4. Validate Datastore Suitability
The destination datastore must be validated not only for free space, but also for the source VM's disk layout. Broadcom KB 380651 explains that the clone wizard validates all source disks before disk customization. That means even disks you do not want in the final clone can still block datastore selection.
If the source VM has large or temporary data disks that should not be carried forward, a clean maintenance-window approach is to detach them temporarily with Remove device, complete the clone, and then reattach them to the source VM if required.
Related storage guide:
5. Respect Large Disk and Format Limits
Broadcom KB 321231 says the maximum supported VMDK size on VMFS-5 is 62 TB. The same KB also says disks greater than 2 TB can only be moved or cloned to compatible host and datastore combinations.
The practical outcome is:
- verify datastore format in large-disk clone scenarios
- do not allocate storage so tightly that there is no room for related operations
- leave operational headroom for snapshots and similar tasks
KB 321231 also notes that linked clone and snapshot-related operations may fail when disks are fully allocated with no remaining space margin.
6. Prevent Network and Identity Collisions
If the clone powers on in the same network segment as the source, you can create IP, hostname, or domain conflicts. In same-VLAN clone workflows, manage NIC connectivity deliberately and decide whether guest customization or manual first-boot changes are required.
If you need repeatable standardized deployments, a template workflow may be the better long-term option.
What Should You Check for Cross-vCenter Clone?
Cross-vCenter clone is more sensitive than a local clone. Broadcom KB 344959 says the source and destination vCenters should be on the same version. When the GUI is used, both vCenters must also be in Enhanced Linked Mode and inside the same SSO domain.
The same KB adds several operational requirements:
- consider 443, 8000, and 902 connectivity requirements
- Distributed Switch -> Standard Switch is not supported
- Distributed -> Distributed, Standard -> Standard, and Standard -> Distributed are supported
That means cross-vCenter clone planning must include version, network type, and connectivity checks together.
Most Common Clone Errors and Fixes
The application pauses briefly after a hot clone
Broadcom KB 420149 says this is caused by temporary snapshot consolidation. High disk I/O makes the stun window worse. The fix is to move hot clone into a low-I/O window or use a cold clone for critical systems.
The target cluster or resource pool cannot be selected
Broadcom KB 409099 points first to the missing Resource Assign virtual machine to resource pool privilege.
Select a valid destination storage
According to Broadcom KB 380651, the wizard validates all source disks before you can remove unwanted ones from the clone design. Temporary disk detachment can be a valid workaround.
Large-disk clone workflows fail or behave unexpectedly
Broadcom KB 321231 shows that host compatibility and datastore format are critical, especially above 2 TB.
Cross-vCenter clone fails because of network mismatch
Broadcom KB 344959 explicitly says that Distributed Switch -> Standard Switch is not supported, so the network design must be validated before starting the clone.
First 20-Minute Checklist
- The source VM was validated as a safe clone source
- If this is a hot clone, a low-I/O maintenance window was chosen
- Destination cluster or resource pool permissions were verified
- Datastore space and disk composition were reviewed
- Large-disk host and datastore compatibility were confirmed
- NIC mapping and IP collision risk were reviewed
- Guest customization or first-boot plan is ready if needed
- Hostname, IP, and service health were verified after first boot
Next Step with LeonX
Cloning creates speed, but without standards it can also multiply the same design flaws. LeonX helps teams connect clone, template, datastore, and network design into a controlled virtualization operating model.
Related pages:
- Hardware & Software Sales
- Managed Services
- Contact
- What Is a VMware VM Template and How Do You Use It?
- How to Create a VMware Cluster
Frequently Asked Questions
What is the main difference between a VMware clone and a template?
A clone is a copy of an existing VM. A template is a controlled golden image for repeatable deployment. Cloning is fast; templates are better for standardization.
Why can hot clone cause a brief interruption?
Broadcom KB 420149 says a powered-on clone uses a temporary snapshot, and the VM can be briefly stunned during consolidation.
Why do I get a resource pool permission error while cloning?
Broadcom KB 409099 says the most common cause is a missing Resource Assign virtual machine to resource pool privilege.
Why does cross-vCenter clone not work with every network type combination?
Broadcom KB 344959 limits supported networking combinations, and specifically says Distributed Switch -> Standard Switch is not supported.
Why can large data disks block the clone wizard before disk customization?
Broadcom KB 380651 says the wizard validates capacity for all source disks before it lets you customize which disks stay in the final clone.
Conclusion
VMware VM cloning is powerful when used deliberately. It can also create I/O stun, permission failures, network conflicts, and datastore surprises if it is treated like a simple copy button. In the September 15, 2025 context, the safest approach is to understand hot clone impact, validate compute and datastore suitability upfront, plan cross-vCenter clone with version and networking rules, and control first boot with a clear checklist.
Sources
- Broadcom KB 420149: Virtual machine becomes temporarily unresponsive during a hot clone operation
- Broadcom KB 409099: Error while cloning a VM: You do not have the privilege 'Resource Assign virtual machine to resource pool' on the selected Cluster
- Broadcom KB 344959: Cross vCenter Migration and Clone requirements in VMware vSphere 6.x and later
- Broadcom KB 380651: How to Clone a Virtual Machine When Source VM Has Disks Too Large for any Storage
- Broadcom KB 321231: Support for virtual machine disks larger than 2 TB in VMware ESXi
- Broadcom KB 326316: VMware vCenter Server versions and build numbers
