Cloning a Virtual Machine to a Template

You may clone a virtual machine to a template once it’s been created. Templates are main copies of virtual machines that allow you to generate virtual machines that are ready to use and not much effort needs to Cloning a Virtual Machine to a Template. While the original virtual machine is preserved, you can make changes to the template, such as adding extra applications in the guest operating system.

After you’ve created a template, you can’t change it. To edit an existing template, first convert it to a virtual machine and then make the required modifications before returning the virtual machine to a expected template. Clone a template to a template to keep the original state of the template.

Read below for more about Cloning a Virtual Machine to a Template.

Before you begin

Using VMware vSphere, you should have created a virtual machine template.
You should have installed the VMware VAAI NFS Plug-in.
Installing the plug-in, while not required, is a best practice since it shifts the workload from the host to the storage system, improving cloning efficiency.

Stop any load generators that are running in the virtual machine before performing the clone procedure.

Also need to verify that you have the following permissions:

Virtual machine>Provisioning>Create template from virtual machine on the source virtual machine.

Virtual machine>Inventory>Create from existing on a virtual machine folder where the template is been created.

Resource>Assign virtual machine to resource pool on the destination VMhost, cluster, or resource pool.

Datastore>Allocate space on all datastores where the template is created.

  • Start the Clone Virtual Machine To Template wizard in vSphere Web Client.
Cloning a Virtual Machine to a Template
Cloning a Virtual Machine to a Template
Cloning a Virtual Machine to a Template
  • Enter a name for the template and a data center or folder to deploy it in on the Select a name and folder page.

The name of the files and folders on the disk is determined by the template name. The template files are called win8tmp.vmdk, win8tmp.nvram, and so on if the template is entitled win8tmp. The names of the files in the Datastore do not change when you update the template name.

Folders are used to hold virtual machines and templates for various groups within an organization, and they may be assigned rights. You may place all virtual machines and templates in a datacenter and organize them differently if you desire a flatter structure.

  • Select a host or a cluster resource for the template on the Select a compute resource page.

The results of the compatibility checks are displayed in the Compatibility pane.

  • Select the datastore or datastore cluster where the virtual machine configuration files and all virtual disks will be stored on the Select storage page. Next should be selected.
    • Select the format for the virtual machine’s disks.

Disk Format Options are:

Thick Provision Lazy Zeroed

Thick Provision Eager Zeroed

Thin Provision

Format of virtual machine disk
  • From the VM Storage Policy drop-down menu, choose a storage policy.

Storage rules define the storage needs for virtual machine applications.

  • Choose the datastore location where the virtual machine files will be stored.

Your choice has an impact on the storage creation procedure.

Storage Options are:

Store all virtual machine files in the same location on a datastore.

Store all virtual machine files in the same location on a datastore.

Store virtual machine configuration files and disks in separate locations.

Store all virtual machine files in the same non-volatile memory disks.

  • Review the template options on the Ready to finish screen before clicking Finish.

In the Recent Tasks window, you can see how far the clone job has progressed. When the task is finished, the template is added to the inventory.

Read more: Virtualization

Leave a Comment

Your email address will not be published.