VM Templates and Images
What a VM Template Is and Why Hosts Use Them
A VM template is a master copy of a virtual machine that has an operating system installed and configured, ready to be copied. Instead of installing an operating system from scratch for each customer, a provider clones the template and starts the copy as a new VM. This takes minutes or less, rather than the much longer time a manual installation needs.
The master copy is often called a golden image. It usually contains the operating system, current security updates, the default packages a customer expects and the monitoring agents the provider runs. Each new server starts from this known-good state, which makes deployments consistent and easier to support.
Images on a host are typically disk files in formats such as qcow2 or VMDK, the same kinds of virtual disk files used for any VM. Providers also publish cloud images, which are ready-made Linux disk images for common distributions that can serve as the starting point for new VMs.
Preparing an Image So Each Clone Behaves Correctly
A clone is an exact copy, so some identity data must be removed from a template before it is cloned. Otherwise every new server may share the same machine ID, SSH host keys or host name. That causes network conflicts and security risks. The removal step is called generalizing. On Windows the usual tool is Sysprep, and on Linux it means clearing machine-specific files before the image is captured.
Cloud-init is a widely used tool that handles first-boot setup. When a new VM starts from a cloud-init-enabled image, it reads settings supplied by the provider or customer, such as the host name, SSH public keys and a startup script, and applies them. This lets one image serve many customers without manual setup.
Clones can be full or linked. A full clone copies the whole disk, so it is independent of the template. A linked clone stores only its own changes and refers to the template's disk for everything else. Linked clones save space and are created faster, but they depend on the template staying in place.
Keeping Templates Up to Date
A template is a snapshot in time. Security updates released after it was built are not in servers cloned from it until the template is rebuilt or the new VMs are patched after deployment. Many providers rebuild their templates on a regular schedule, so new customers start from a recent image.
Changing a template does not change the VMs already cloned from it. Existing servers need their own patching and maintenance. A template is therefore a starting point for new servers, not a substitute for ongoing maintenance.
Frequently asked questions
What is the difference between a VM template and a snapshot?
A template is a master copy meant to be cloned into many new VMs and is usually kept unchanged. A snapshot is a saved state of one specific VM that you can roll back to. Templates are used to create servers, while snapshots are used to undo changes on a server that already exists.
Can a VM template be used on any host?
Usually only on hosts whose hypervisor can read the image's disk format. A qcow2 file suits KVM-based hosts, while VMDK and VHDX files are used with VMware and Microsoft Hyper-V. Converting between formats is possible, but it adds delay and should be tested before the image is used for customers.