Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Diagnosing slow deployment of templates or clones from vCenter Server

Symptoms

  • Slow deployment of templates from within vCenter Server
  • Slow deployment of clone in vCenter Server
  • You are experiencing high CPU utilization on the ESX host
  • You are experiencing high memory utilization on the ESX host
  • Slow response when administering an ESX host
  • Slow performance when copying files between shared VMFS storage (fibre-channel SAN) and local VMFS storage

Purpose

This document guides you through the process of troubleshooting slow deployment of templates from vCenter Server. It helps you eliminate the common causes for your problem by verifying the scope of the problem as well as the networking and storage configuration of the ESX.

Resolution

Please validate that each troubleshooting step below is true for your environment. Each step will provide instructions or a link to a document, in order 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. Please do not skip a step.
  1. Verify if the slow deployment is specific to one template or if it affects all templates. To properly test this,VMware recommends to create a brand new template and test the deployment. This provides a clean test of the environment. For more information if template deployment is slow for a single template, see Deploying a single template is slow (1004028).

  2. Verify that no processes are over utilizing the resources on the ESX service console.  For more information, see Checking for resource starvation of the ESX Service Console (1003496).

  3. Verify that the network configuration on the ESX host is optimized for the best performance, including speed and duplex settings. For more information, see Configuring the speed and duplex of an ESX/ESXi host network adapter (1004089).

  4. Verify that the firmware on the RAID controller or HBA is up to date. For more information, see Slow performance caused by out of date firmware on a RAID controller or HBA (1006696).

  5. Verify that the local storage or SAN array is configured correctly. For more information, see Slow performance caused by misconfigured local storage or SAN array (1006602).


  6. Verify on ESX/ESXi 4.1 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:
Note: If your problem still exists after trying the steps in this article, please:

Tags

deploy-template  template-deployment  slow-template-deployment

See Also

Update History

<pre>03/9/2011 - Added additional information about VAAI. </pre>

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
Actions
  • Bookmark Document
  • Email Document
  • Print Document
  • Subscribe to Document
  • Bookmark and Share