To work around this issue:
- Deploy the virtual machine from a template.
- When the virtual machine is deployed, SSH into the host on which it resides.
- Change directory to the where the virtual machine resides on the datastore.
- Clone the .vmdk to an RDM with a command similar to:
vmkfstools -i /vmfs/volumes/datastorename/foldername/vmname.vmdk -d rdm:/vmfs/devices/disks/naa.referencenumber
- Edit the settings of the virtual machine and remove the original hard disk
- Add an existing hard disk and point to the new cloned .vmdk file.
- Power on the virtual machine.
This process powers up the new virtual machine successfully and the customization should proceed, if selected. After the virtual machine has been successfully created and validated, you can delete the original .vmdk file from the virtual machine's folder using the rm -f command.
Caution: The rm c command permanently deletes the .vmdk file.