{"id":316,"date":"2026-01-23T02:00:04","date_gmt":"2026-01-23T02:00:04","guid":{"rendered":"https:\/\/virtualserversvps.com\/blog\/?p=316"},"modified":"2026-07-27T22:09:00","modified_gmt":"2026-07-27T22:09:00","slug":"how-to-fix-and-enable-virtualization-kvm-in-your-server-or-vps","status":"publish","type":"post","link":"https:\/\/virtualserversvps.com\/blog\/how-to-fix-and-enable-virtualization-kvm-in-your-server-or-vps\/","title":{"rendered":"How to Enable KVM Virtualization on Your VPS: Check CPU Support, Load Kernel Modules, and Verify Acceleration"},"content":{"rendered":"\n

KVM (Kernel-based Virtual Machine) turns your Linux VPS into a Type-1 hypervisor, letting you run nested virtual machines with near-native performance. Whether you need to test different operating systems, isolate development environments, or run Docker containers that depend on hardware acceleration, enabling KVM is a foundational skill. If you are evaluating providers that support nested virtualization, compare VPS performance across the top hosting companies<\/a> to find one that meets your needs. This guide walks through checking CPU support, loading the necessary kernel modules, verifying that KVM acceleration is active, and troubleshooting the most common errors.<\/p>\n\n\n\n

Prerequisites<\/h2>\n\n\n\n

Before you begin, confirm you have root or sudo access to a Linux VPS running a modern kernel (5.x or newer). Most VPS providers use KVM as their underlying hypervisor, so nested KVM is typically available unless the provider explicitly disables it in their virtualization layer. Ubuntu 24.04 LTS, Debian 12, and Rocky Linux 9 are all well-supported options.<\/p>\n\n\n\n

Step 1: Check CPU Virtualization Extensions<\/h2>\n\n\n\n

The first thing to verify is whether your CPU supports hardware virtualization. Run this command:<\/p>\n\n\n\n

grep -E --color=auto '(vmx|svm)' \/proc\/cpuinfo<\/code><\/pre>\n\n\n\n
If you see vmx<\/code> (Intel) or svm<\/code> (AMD) in the flags section, your CPU supports virtualization. If nothing appears, either your CPU lacks hardware virtualization support \u2014 which is rare on modern VPS hardware \u2014 or the feature is disabled at the hypervisor level. In that case, contact your VPS provider and ask whether they support nested virtualization or custom kernel modules. Some providers like Hetzner, Vultr, and Linode allow nested KVM on specific plans.<\/p>\n\n\n\n
You can also check with this one-liner:<\/p>\n\n\n\n
kvm-ok<\/code><\/pre>\n\n\n\n
If kvm-ok<\/code> is not installed, get it with sudo apt install cpu-checker<\/code> (Debian\/Ubuntu) or sudo dnf install cpu-checker<\/code> (RHEL\/Rocky). It will tell you in plain English whether KVM acceleration can be used.<\/p>\n\n\n\n
Step 2: Load KVM Kernel Modules<\/h2>\n\n\n\n
Once you confirm virtualization support, load the KVM kernel modules:<\/p>\n\n\n\n
sudo modprobe kvm\nsudo modprobe kvm_intel   # for Intel CPUs\nsudo modprobe kvm_amd     # for AMD CPUs<\/code><\/pre>\n\n\n\n
Load the one that matches your CPU architecture. Verify the modules are loaded:<\/p>\n\n\n\n
lsmod | grep kvm<\/code><\/pre>\n\n\n\n
You should see output showing kvm<\/code> and either kvm_intel<\/code> or kvm_amd<\/code> along with their usage counts. If the module fails to load with a “Operation not permitted” error, your VPS provider has disabled nested virtualization at the host level and you will need to use QEMU without KVM acceleration (slower but functional).<\/p>\n\n\n\n
Step 3: Make KVM Modules Persistent Across Reboots<\/h2>\n\n\n\n
Add the KVM modules to your system’s module configuration so they load automatically on boot:<\/p>\n\n\n\n
echo 'kvm' | sudo tee \/etc\/modules-load.d\/kvm.conf\necho 'kvm_intel' | sudo tee -a \/etc\/modules-load.d\/kvm.conf\n# or for AMD:\n# echo 'kvm_amd' | sudo tee -a \/etc\/modules-load.d\/kvm.conf<\/code><\/pre>\n\n\n\n
Step 4: Install KVM and Management Tools<\/h2>\n\n\n\n
Install the full KVM stack along with management tools:<\/p>\n\n\n\n
On Ubuntu\/Debian:<\/strong><\/p>\n\n\n\n
sudo apt update\nsudo apt install qemu-kvm libvirt-daemon-system libvirt-clients bridge-utils virt-manager -y\nsudo usermod -aG libvirt $USER<\/code><\/pre>\n\n\n\n
On Rocky Linux\/RHEL 9:<\/strong><\/p>\n\n\n\n
sudo dnf install qemu-kvm libvirt libvirt-daemon-kvm virt-install -y\nsudo systemctl enable --now libvirtd\nsudo usermod -aG libvirt $USER<\/code><\/pre>\n\n\n\n
Log out and back in for the group changes to take effect.<\/p>\n\n\n\n
Step 5: Verify KVM Acceleration Is Working<\/h2>\n\n\n\n
After installation, confirm that KVM acceleration is active:<\/p>\n\n\n\n
virt-host-validate<\/code><\/pre>\n\n\n\n
This command checks all aspects of virtualization readiness and reports PASS, WARN, or FAIL for each check. You want to see PASS for “QEMU: Checking for hardware virtualization” and “QEMU: Checking if device \/dev\/kvm exists.” You can also check for \/dev\/kvm directly:<\/p>\n\n\n\n
ls -la \/dev\/kvm<\/code><\/pre>\n\n\n\n
If \/dev\/kvm<\/code> exists with permissions crw-rw----<\/code>, acceleration is active and your user has access to it.<\/p>\n\n\n\n
Step 6: Create Your First KVM Guest<\/h2>\n\n\n\n
With KVM acceleration verified, create a test virtual machine using virt-install. This command launches a 2 GB RAM, 2 vCPU Debian 12 VM using KVM acceleration:<\/p>\n\n\n\n
sudo virt-install \\\n  --name debian-test \\\n  --ram 2048 \\\n  --vcpus 2 \\\n  --disk size=10 \\\n  --cdrom \/path\/to\/debian-12.iso \\\n  --os-variant debian12 \\\n  --network default \\\n  --graphics vnc \\\n  --console pty,target_type=serial<\/code><\/pre>\n\n\n\n
If the guest boots successfully and runs without significant slowdown, KVM acceleration is working correctly. You can manage your guests with virsh list --all<\/code> or through the Cockpit web interface if you prefer a GUI.<\/p>\n\n\n\n
Troubleshooting Common Issues<\/h2>\n\n\n\n