🚀 Getting Started
Installing Virtlix on a Fresh Server
Server Requirements & Partition Layout
Activating Your License
Your First VPS
🖥️ VPS Management
Creating and Configuring a VPS
Cloning and Rebuilding a VPS
Creating a Reusable Template from a VPS
Resource Plans and Per-VM Limits
Windows Guest Support
Rescue Mode: Recovering a Broken VPS
📦 LXC Containers
LXC Containers: What They Are and When to Use Them
Creating and Managing an LXC Container
LXC Container Limitations vs KVM
🌐 Networking & Firewall
IP Pool and Network Modes
VPS Firewall Rules
Server-Level Firewall Plans
Console Access: noVNC and the Web Terminal
Network Filtering: Anti-Spoofing and Rogue RA Protection
IPv6 Dual-Stack Networking
Power DNS Integration and Reverse DNS Zones
Adding Multiple IPs and Per-IP MAC Overrides
💽 Storage & Hardware
Storage Pools: Local Disk and Remote NFS
PCI and USB Device Passthrough
Attaching Extra Volumes to a VPS
💾 Backups & OS Templates
Automated Backups and Backup Destinations
Managing OS Templates
Uploading and Using ISOs
Media Groups
🔑 Multi-Server & Licensing
Understanding Your License and VPS Limits
Master Configuration and Security Settings
Registering and Controlling Remote Servers
Webhook Callbacks
Selling VPS Hosting Through WHMCS
🔐 Account & Security
Two-Factor Authentication
Docs /
Getting Started /
Your First VPS
Your First VPS
Once the panel is up, go to Virtual Machines → Create VPS. You'll need at minimum:
- A name and hostname for the guest.
- An OS template - Virtlix ships with common templates pre-listed; the first one you pick downloads and caches on first use, so it'll take a minute or two, after which every future VPS on that same OS is near-instant (guests are copy-on-write overlays on top of the cached base image).
- CPU / RAM / disk sizing, and an owner if you're creating it on behalf of a reseller or end-user.
- Either an SSH key or a root password for initial access.
IP assignment is automatic from whatever's free in your IP Pool unless you pick one manually. Once created, the VPS shows a creating status while the disk is built and cloud-init runs, then flips to running.
From the VPS's own page you get console access (noVNC), a web terminal, and controls for start/stop/reboot/reinstall - everything you'd expect without needing to touch virsh directly.