Cloud-init & OS templates
Serve your own cloud-init OS library. Define base images and native cloud-init config once; the panel stages images on managed per-node storage and downloads them on demand.
What it does
The capabilities behind this feature, all self-hosted, all in one panel.
Editable templates
Each template is a base image URL plus native cloud-init: user, SSH keys, IP, nameserver, upgrade, root-SSH, no hard-coded resources (those are Plans).
Branded groups
Organise templates into admin-defined groups with an uploaded image; the create and reinstall wizards show the same visual group picker.
Managed image storage
A dedicated nexovirt-images storage is provisioned on every node; QEMU images are downloaded on demand by the host agent and cleaned up after use.
Cloud-init delivered correctly
A qemu-guest-agent cloud-init vendor snippet is delivered through the host-agent job queue, degrading gracefully to native cloud-init with a warning when no agent is present.
How to use it
Up and running in a few steps.
-
In Settings → OS templates, create a group and add templates (base image + cloud-init).
-
Test an image URL right from the row to confirm it downloads on the host.
-
Pick the template in the create or reinstall wizard: the panel stages and imports it.
Related features
Free Community Edition
Be first to run NexoVirt
Start managing all your Proxmox hosts from one panel.