ProxCP KVM Templates

From ProxCP Documentation


ProxCP offers support for KVM creation and rebuilding from templates. Pre-built ProxCP KVM templates are available on our template distribution site. You are not required to use these templates but these are the only templates we offer support for.

Proxmox does not currently offer a mechanism to share KVM templates between Proxmox nodes. Therefore, you need to download our KVM templates onto every Proxmox node individually. To make managing this easier, use the same Proxmox VMIDs for every KVM template between Proxmox nodes. For example, if you have a CentOS 7 template, try to make the template VMID the same number on all Proxmox nodes.

If you followed our recommendation to assign VMID ranges to Proxmox nodes, the VMIDs of your KVM templates should be less than the VMID range.

  • Continuing our example with node1 (VMID range 1000-2999), the KVM template VMIDs on node1 should be less than 1000

KVM Templates - Admin

In the ProxCP KVM Templates Admin menu, you can set the template VMID on a per-node level. It is possible that the same KVM template will have a different VMID on different Proxmox nodes.

As of writing, all ProxCP Linux KVM templates support Cloud-Init.

This page allows Admins to delete KVM templates from ProxCP. This action only removes the template from ProxCP and does not remove the template VM from the Proxmox node.

KVM Templates Installation

  • Download the desired template from our distribution site to your Proxmox server (i.e. wget)
  • Run the following command on your Proxmox server
qmrestore {template file} {VMID}

The restored VM should appear in Proxmox as a template with all correct settings already. Then, add the template in ProxCP.

Creating Your Own KVM Templates

Creating Your Own ProxCP KVM Templates

Proxmox VE 5.x Notes

  • You may need to delete and re-create the cloud-init drive depending on the Proxmox VMID you chose.

Proxmox VE 6.x Notes

  • The qmrestore command will fail in Proxmox 6.x unless template files are named a specific way.
Example: centos-7-amd64.vma.lzo must be renamed to vzdump-qemu-200-2020_06_10-10_00_00.vma.lzo
Required format: vzdump-qemu-{vmid}-{year}_{month}_{day}-{HH}_{MM}_{SS}.vma.lzo
  • The VMID in the vzdump file name and the qmrestore command must match