VIRTLIX LICENSE MANAGER
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
🌐 Networking & Firewall
IP Pool and Network Modes VPS Firewall Rules Server-Level Firewall Plans Console Access: noVNC and the Web Terminal
💾 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
❓ Troubleshooting & FAQ
Console Shows "Connection Lost" License Shows as Suspended or Expired VPS Won't Start After Creation Common Questions
Docs / Troubleshooting & FAQ / VPS Won't Start After Creation

VPS Won't Start After Creation

Two things account for nearly every case of a VPS stuck in creating or failing to boot:

  1. No hardware virtualization on the host - check egrep -c '(vmx|svm)' /proc/cpuinfo. If it returns 0, libvirt can't start KVM guests at all, and this needs enabling in the host's BIOS (or, if the host is itself a VM, nested virtualization needs to be turned on by whoever manages that outer host).
  2. OS template still downloading - the very first VPS created on a given OS has to wait for that template to finish downloading and caching. Check /var/log/virtlix-install.log or the OS Templates page for download progress; every VPS after that first one on the same OS is fast, since it reuses the cached base image.

If neither applies, check storage/logs/laravel.log on the panel itself for the actual libvirt error - it's almost always more specific than "won't start."