VIRTLIX
Home Features Docs Pricing Changelog About Contact Login
🚀 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
❓ Troubleshooting & FAQ
Console Shows "Connection Lost" License Shows as Suspended or Expired VPS Won't Start After Creation Common Questions Can't SSH Into a New LXC Container PCI Passthrough Device Not Working NFS Storage Pool Won't Mount OS Template Download Stuck or Failed
Docs / LXC Containers / LXC Container Limitations vs KVM

LXC Container Limitations vs KVM

LXC containers are a genuinely useful second backend, but they're deliberately narrower than KVM in a few ways - worth knowing before you pick a virtualization type for a given workload:

  • No console/VNC access - a container has no virtual hardware to display, so there's no graphical console the way a KVM guest has. SSH is the only way in once networking is up.
  • No backups or cloning yet - the automated backup system and "clone a VPS" feature are currently KVM-only.
  • No extra volumes or PCI/GPU passthrough - both of those attach virtual/physical hardware to a VM in a way that doesn't have a container equivalent yet.
  • No "Create Template from VPS" - turning a running guest into a reusable template currently only works for KVM's disk-image-based guests.
  • Linux only - a container shares the host's kernel, so Windows (or any non-Linux OS) isn't possible under LXC. Use KVM for Windows guests.

None of these are permanent architectural limits - they're just not built yet. The panel is explicit about each one wherever it applies (e.g. the Console tab explains why it's unavailable for a container VPS, rather than just failing silently), so it should never be a surprise when one of these doesn't work for an LXC guest.