Cloned virtual machine's .vmdk file refers to its source virtual machine's .vmdk file

Products

• VMware vSphere ESXi

Issue/Introduction

After the clone task finished, from target virtual machine's, you can see "scsi0:0.file Name" refers to the source virtual machine's vmdk file.

Steps to reproduce this:

1. Right click the source vm (powered-on vm) in the inventory --> clone --> clone to virtual machine.
2. Choose the same esxi host with source VM.
3. Change to a different storage.
4. Select "customize this virtual machine's hardware" but don't change virtual hardware on the next step.

Environment

VMware vSphere 7.0.x
VMware vSphere 6.7.x

Cause

This is a known issue and is seen when the clone operation matches the conditions specified above.

Resolution

Broadcom is aware of this issue and currently there is no resolution.
 

Workaround #1:

• Edit a virtual machine's hardware after the cloning task is completed, ensure that the "Customize this virtual machine's hardware" box is unchecked during the cloning process. This allows you to make hardware adjustments after the clone has finished.

Workaround #2:

• Power off the virtual machine before performing clone.

Workaround #3:

• Manually correcting the reference of vmdk to point to the new virtual machine's vmdk file.
  Add an Existing Hard Disk to a Virtual Machine
  
  

Workaround #4:

• Clone the virtual machine and select the same storage as the original storage. This will not cause the issue and will mount the new cloned vmdk after the cloning completes.
  Clone a Virtual Machine