Troubleshooting template deployment or cloning when it fails in vCenter Server

Products

• VMware vCenter Server

Issue/Introduction

This article provides troubleshooting steps for template deployment and cloning in vCenter Server failures. These steps eliminate common causes for the problem by verifying the sysprep files, verifying the virtual machine configuration, and verifying the the vCenter Server configuration.

Symptoms:

• Deploying a template fails
• Cannot deploy a virtual machine
• Failure when cloning virtual machines
• Failure to boot guest operating system after installing VMware Tools
• Cannot clone a virtual machine
• You see errors similar to:
  
  Network copy failed for file.
  [] /home/vmware/xxx/nvram
  
  
• When attempting to clone a virtual machine through vCenter Server, you see the error:
  
  Failed to connect to host

Environment

VMware vCenter

Resolution

Validate that each troubleshooting step below is true for your environment. Each step provides instructions or a link to a document to eliminate possible causes and take corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. Do not skip a step.

1. Name resolution problems in the ESX/ESXi environment can cause issues with file copies. Verify that Name Resolution is valid on ESX/ESXi. For more information, see Identifying issues with and setting up name resolution on ESX/ESXi Server (1003735).
   
   
2. The correct version of sysprep is critical in deployments. Verify that the correct version of Microsoft sysprep has been installed to properly do the customization.
   
   
3. Verify that virtual machines are installed with the latest version of VMware Tools. For more information, see Verifying a VMware Tools build version (1003947).
   
   
4. In some cases, other VMware products can interfere with the normal operation of vCenter Server. Verify that no other VMware products have been installed on vCenter Server.
   
5. Verify that the guest operating system is defined correctly. Incorrect definitions can cause deployment failures. For more information, see How to Verify if the Configured Guest OS details are matching with the installed OS details in a VM.
   
   
6. Verify if the slow deployment is specific to one template or if it affects all templates. To properly test this,VMware recommends you to create a brand new template and then test the deployment. This provides a clean test of the environment.
   
   
7. Determine if the issue is caused due to conditions related to slow cloning or deployment of templates. 

Note: If your problem still exists after trying the steps in this article, please:

• Gather the VMware Support Script Data. For more information, see Collecting diagnostic information for VMware products (1008524).
• File a support request with VMware Support and note this KB Article ID in the problem description. 

Additional Information

 if the storage array devices in the environment support the hardware acceleration functionality and if they are responding correctly to VAAI primitives. If there is no VAAI support on the array, cloning or Storage vMotion may fail at 18%. For more information see Cloning or Storage vMotion fails at 18% with the error: Failed to clone: Connection timed out (1029244).

 

For further information on VAAI, see:

• Frequently Asked Questions for vStorage APIs for Array Integration (1021976)
• Disabling the VAAI functionality in ESXi/ESX (1033665)

Identifying issues with and setting up name resolution on ESX/ESXi Server
Verifying a VMware Tools build version
Ensuring the guest operating system type is set correctly
Collecting diagnostic information for VMware products
Cloning or Storage vMotion fails at 18% with the error: Failed to clone: Connection timed out