VirtConsole 3.2.0 is the first release to carry the new name in the product itself - and it brings a batch of features we have been building, a more resilient base, and a simpler install. Same product, same roadmap, under a name we can own.
The rename reaches the product
The panel, installer and documentation now read VirtConsole, and our services move to virtconsole.com. The previous hypervisor.io addresses keep working throughout the transition, so nothing breaks while you move. The full reasoning is in Hypervisor is becoming VirtConsole.
New in this cycle
3.2.0 also brings the features we have been building, now under the VirtConsole name:
- Windows licensing. Activate Windows guests from your own SPLA keys, entered once in the panel. Activation is handled for you when a Windows VM deploys - your keys stay in the platform and are never exposed to the guest or the customer.
- Managed SSL certificates. Issue and manage certificates at the account level, serve multiple certificates from a single managed load balancer with SNI, and get Let’s Encrypt issuance and renewal handled for you - with alerts before anything expires.
- Support desk. A built-in ticketing system with SLA tracking, file attachments (scanned and previewable in-browser), and optional AI-assisted triage.
- System DNS. Host and manage public DNS zones, with delegation checks that tell you exactly what is misconfigured.
- Import Doctor. Import VMs from other platforms - including Windows guests - and have driver and boot issues detected and repaired offline, so they come up cleanly on VirtConsole.
- Monitoring & alerts. Alert rules across your resources, including certificate-expiry and capacity signals.
More resilient licensing
Licensing carries cleanly through in-place upgrades and backups now, with nothing for you to do - paid nodes stay paid across updates.
One installer, every supported OS
The three per-OS install scripts are now a single install.sh that detects the distribution and does the right thing across Debian 11/12/13, Ubuntu 22.04/24.04/26.04 and RHEL-family 9/10 (Rocky, Alma, CentOS Stream). Fresh installs are one line:
curl -fsSL https://packages.virtconsole.com/master/install.sh | sudo bash # control panel
curl -fsSL https://packages.virtconsole.com/slave/install.sh | sudo bash # hypervisor nodeFixes and hardening
- Private DNS inside VPCs now resolves reliably regardless of a node’s install path - the per-VPC resolver is rewritten to the node’s own layout on every sync.
- Numerous rebrand-path and configuration-consistency fixes across the installer, updater and service configuration.
Upgrading an existing install
3.2.0 also relocates the install to the virtconsole layout. For this transition, apply it with a single command on each node, run as root - your hypervisor nodes first, then the control panel:
curl -fsSL https://packages.virtconsole.com/virtconsole-migrate.sh | sudo DEPLOY_RELEASE=1 bashThe same command works on both roles - it detects whether it is running on a control panel or a hypervisor node and pulls the matching release. It downloads 3.2.0, deploys it, runs migrations, and migrates the install in place to /opt/virtconsole. Your VMs, data, license, configuration and pricing are preserved. Run the hypervisor nodes first so the control panel finds them ready.
Thanks for building on VirtConsole. Questions or trouble upgrading - reach us any time.