A VPS platform has two layers to keep current: the Virtualizor panel software and the host operating system with its kernel, QEMU and libvirt. Panel updates are usually quick and invisible to customers; host updates that need a reboot affect every VPS on the node and must be planned.
Before you start
- Root access to the master and all slave nodes.
- Recent backups of customer VPS; see backup servers and plans.
- Out-of-band access (IPMI/iDRAC) to each node in case a reboot fails.
Update the Virtualizor panel
- In the admin panel go to Configuration → Updates (or Update Virtualizor).
- Choose the update channel – Stable for production.
- Enable Auto Update for panel updates if you prefer, or click Update Now to install the latest version.
- Update the master first, then each slave. Keep all servers on the same version.
Panel updates do not restart virtual machines. Read the release notes for changed defaults or new requirements.
Update the host OS
On each node, install security updates regularly:
dnf -y update(or apt update && apt -y upgrade on Ubuntu). Updates to QEMU take effect only when each VM is restarted; kernel updates need a node reboot.
Plan a node reboot
- Schedule a maintenance window at a quiet time and give customers notice – at least a few days for planned work.
- Notify customers on that node. With WHMCS, use the Mass Mail Tool filtered by server and post a Network Issue; see mass mail and reports.
- Optionally migrate important VPS to another node beforehand; see add slave servers.
- Reboot the node. Virtualizor starts VPS that were running before, if Start VPS on boot is enabled in the master settings.
- Check Virtual Servers → List VPS for servers that did not start and start them manually.
Routine maintenance checklist
- Watch free space in the LVM volume group and on backup servers.
- Review RAM overcommit and CPU load per node in the dashboard.
- Remove end-of-life OS templates and add new releases; see OS templates.
- Check disk health with
smartctland RAID status. - Renew the panel SSL certificate (automatic with Let's Encrypt) and the Virtualizor licence.
- Review admin logins and API keys.
Troubleshooting
- Panel update fails: check disk space and connectivity to Virtualizor's update servers; rerun the update.
- Node does not come back after reboot: use IPMI to view the console; common causes are network bridge configuration and old kernels.
- VPS stay offline after reboot: autostart disabled or storage not mounted; start them and fix the setting.
- Master and slave out of sync: update both to the same version.