Linux VPS

Proxmox templates and clones: linked clone vs full clone

Turn a prepared VM into a Proxmox template, choose between linked and full clones, clean machine IDs before cloning, and deploy new VMs in seconds.

IntermediateProxmox VE2 min read

Installing every VM from an ISO wastes time. With Proxmox templates you prepare one VM, convert it into a read-only template and clone it whenever you need a new server. The main choice is between linked and full clones.

Before you start

  • A VM with the OS installed, updated and with the QEMU guest agent (create a VM).
  • For cloud images with automatic IP and SSH key setup, see cloud-init templates.

Prepare the VM

  1. Install updates and your standard tools.
  2. Remove unique identifiers so clones do not clash. On Linux:
truncate -s 0 /etc/machine-id && rm -f /var/lib/dbus/machine-id
rm -f /etc/ssh/ssh_host_*

Make sure SSH host keys are regenerated on first boot (Debian/Ubuntu: dpkg-reconfigure openssh-server in a first-boot script, or cloud-init does it for you). On Windows, run Sysprep with Generalize and shut down.

  1. Shut down the VM.

Convert to a Proxmox template

Right-click the VM and choose Convert to template, or run qm template 9000. Templates cannot be started, which protects them from changes.

Linked clone vs full clone

Linked cloneFull clone
Creation speedSecondsCopies the whole disk
Disk spaceOnly stores changesFull size per VM
Depends on templateYes, template cannot be deletedNo, fully independent
StorageNeeds snapshot-capable storage (LVM-thin, ZFS, Ceph, qcow2)Any
Best forLabs, test VMs, short-lived serversProduction servers

Clone a template

  1. Right-click the template → Clone.
  2. Set the new VM ID and name, and choose Mode: Linked Clone or Full Clone.
  3. For full clones, choose the target storage.
  4. Click Clone, then adjust CPU, RAM and network before starting.
qm clone 9000 130 --name app1 --full

Tip: Rebuild your template every few months with fresh updates so new VMs do not start out of date.

Troubleshooting

  • Clones have the same IP from DHCP: the machine ID was not cleared before templating.
  • Linked clone option missing: the template's storage does not support it.
  • Cannot delete template: linked clones still depend on it.

Frequently asked questions

Can I edit a template later?

Clone it to a VM, change it, and convert that VM into a new template.

Are containers cloned the same way?

Yes, LXC containers can be templates and cloned too.

Should production VMs be linked clones?

Full clones are safer, since they do not depend on the template's disk.

Next steps

Was this guide helpful?

Still stuck?

Ask MdmHost AI for a quick answer, or open a ticket and our team will take a look. We are here 24/7.