VMware

VMware VirtualCenter 1.1 Support Documentation


Features | Documentation | Knowledge Base | Discussion Forums

previous Prev   Contents   Last   Next next

Preparing for Templates

Prior to creating a template:

Specifying an Upload Directory for Templates

Specifying an Upload Directory for Templates

When you import a template, you have the option to keep the source virtual machine in its original location or have a copy placed into a host located within VirtualCenter.

When you import a template and select the upload directory option, the new template is copied to the upload directory location. The upload directory must be in a location relative to the VirtualCenter server and local to the VirtualCenter server. It cannot be a network share that is mapped as a local drive.

When you create the template you must have Virtual Machine Administrator or greater role permission on the host. When you deploy a template from the upload directory, you must have Virtual Machine Administrator or greater role permission on the target host.

Note: If you change the upload directory, all subsequently created templates are stored in the new template upload directory. Templates stored in the old upload directory continue to work.

Note: The template upload directory cannot reside on a network share.

To specify a location for importing templates:

  1. From the VirtualCenter client, open the VMware VirtualCenter Settings dialog and select the Templates tab.

    Select File > VMware VirtualCenter Settings.

  2. Enter the template upload directory location. Click OK.

    1. Scroll to the Template Upload Directory field.
    2. Enter the full absolute path of the directory to use as the upload directory.

      This path references a directory to which VirtualCenter has access.

      The path is the location of templates upload directory. It must be a directory local to VirtualCenter server. It must not be a network share mapped locally. It must be a valid directory path and the directory must exist. Set the template upload directory before you create any templates.

Configuring Datastores on GSX Server Hosts

Configuring Datastores on GSX Server Hosts

When a GSX Server host is added to VirtualCenter, the Add a Host wizard defaults the datastore location for all the virtual machines on that host. Only one datastore is allowed per GSX Server. All virtual machine files are stored at the root directory where GSX Server is installed on its host if the datastore is not specified.

Note: You do not set datastores for an ESX Server host through VirtualCenter. Datastores on an ESX Server are the VMFS volumes that are set when you configured the ESX Server. Refer to your ESX Server documentation for information on configuring VMFS volumes.

To specify a different directory location for the datastores of a particular GSX Server:

  1. Select and verify the host is a GSX Server host.

    View the host summary page. The title bar lists the host name, host type (GSX Server or ESX Server), and the virtualization platform version.

  2. Open the Host Properties box. Select the Datastore tab.

  3. In the field, type the name of the datastore and the path to the datastore.
    • This must be in the appropriate format, Linux or Windows path for a GSX Server and as a vmfs-label:disk-name for an ESX Server system.

      To view the format, check the Host Summary page, Datastore field. The path specified there is appropriate for the host type, Linux or Windows.

    • The VirtualCenter user must have read and write permissions on the directory selected.

      Specify the template location as a URL that is on a Network Attached Storage (NAS) local network location.

    • This must be a local directory.
    • Each GSX Server host is allowed one datastore.
Using a GSX Server or Workstation Virtual Machine as a Template

Using a GSX Server or Workstation Virtual Machine as a Template

To use a virtual machine that is already configured as a template:

  1. Power down the virtual machine.
  2. If you have a Workstation or an older GSX Server virtual machine:
    • Upgrade the virtual machine to Workstation 4.0 or GSX Server 2.5 or later, if needed.
    • The source virtual machine must be local to the VirtualCenter server.
    • If the source virtual machine is not local, you must copy the virtual machine to a folder local to the VirtualCenter server.

      Using the method of your choice, copy the contents of the virtual machine folder. The contents include, but are not limited to, the following files:

      Virtual machine configuration file with a .vmx or .cfg extension.

      Virtual disk files with a .vmdk or .dsk extension. There could be several virtual disk files. Copy all of them.

      Note: Edit the disk location of any disks that were specified with absolute paths. When you update the paths to the disk you can use relative or absolute paths to specify the new location of the disks.

      Note: If the source machine has IDE disks it cannot be used as a template for ESX Server or GSX Server hosts.

  3. Proceed to Creating Templates.
Using an ESX Server Golden Image as a Template

Using an ESX Server Golden Image as a Template

To use an existing ESX Server golden image as a VirtualCenter template:

  1. Use your standard ESX Server procedures to import the golden image and create a virtual machine.

    Refer to your ESX Server documentation for additional information.

  2. If the ESX Server host is an unmanaged host, proceed to Using an Unmanaged Virtual Machine as a Template.

    If the ESX Server host is a managed host, proceed to Using a Managed Existing Host Virtual Machine as a Template.

Using an Unmanaged Virtual Machine as a Template

Using an Unmanaged Virtual Machine as a Template

To use an existing virtual machine on an unmanaged host as a template:

  1. Power down the virtual machine.
  2. If you have a virtual machine that resides on a host that is not managed with VirtualCenter, perform the following:
    • Upgrade to ESX Server 2.0.1 or later. or GSX Server 3.1

      Refer to your host virtualization platform documentation for additional information.

    • Temporarily register the ESX Server or GSX Server host with the virtual machine that is the source for the template.

      You may need to adjust to your managed hosts to ensure you have sufficient VirtualCenter licenses.

    • Create the template, by selecting the Copy files to template upload directory option.

      Refer to Creating Templates for information on creating the template.

    • Unregister the ESX Server or GSX Server host.

      Note: If a host that has a templates stored locally (not in the template repository) is removed from VirtualCenter, all the templates are also removed. Returning the host to VirtualCenter does not re-register the templates.

  3. Proceed to Creating Templates.
Using a Managed Existing Host Virtual Machine as a Template

Using a Managed Existing Host Virtual Machine as a Template

To use a managed ESX Server or GSX Server virtual machine as a template:

  1. Power down the virtual machine.
  2. Proceed to Creating Templates.

previous Prev   Contents   Last   Next next