An OS template supplies the starting disk contents and configuration for new Virtualizor guests. Use a supported, trusted image with an identifiable release and verify its behavior before customers can deploy it. A template can distribute security mistakes as quickly as useful configuration.
IN THIS ARTICLE
Check access and requirements
Confirm virtualization type, architecture, supported guest release and required disk layout. Obtain the image from the vendor or your controlled build process and verify its integrity. Do not turn a customer VPS into a public template without removing private data and reusable credentials.
01 Add and validate an OS template in Virtualizor
- Open Media > Add OS Template, choose the intended virtualization type and supply the trusted image source or local template.
- Enter accurate operating-system metadata and compatibility settings. Enable platform operations only when the image layout and guest support have been tested for password, hostname and disk operations.
- Restrict the template to an administrative test audience or media group while validating it. Preserve the existing production template as a separate release.
- Create two disposable VPSs. Check their unique identities, credentials, networking, drivers and first-boot processing. Test a restart and the specific panel operations you intend to offer.
- If producing your own template, follow Media > Create Template on a deliberately prepared, stopped build guest. Keep the build recipe and audit the resulting image for secrets before publishing it.
Will replacing a template patch existing VPSs?
No. Running guests retain their own disks and need normal patch management. Reinstallation from a newer template is a separate operation that can erase existing guest data.
Confirm the expected result
Confirm both test guests have distinct SSH host keys or equivalent OS identity, the expected storage size and usable administrative access. Check that updates work from trusted repositories and no build account or private application content survives.
Resolve setup problems
For failed template creation, inspect the protected creation log and storage compatibility. For a failed guest operation, inspect the template layout and supported guest configuration rather than blindly modifying partitions on a live server. Withdraw an unsafe template from new provisioning and replace it with a versioned corrected image.