Learn why you see error kvm virtualisation configured but not available and how to resolve it with BIOS, modules, CPU checks, and configuration steps. Our Live Support team is always here to help you.

Getting Past the error kvm virtualisation configured but not available Message

Seeing the error kvm virtualisation configured but not available can be frustrating, especially when you expect your virtual machines to just work. The system might be ready for KVM, but something in the background isn’t aligned. This results in failed VM startups, higher resource usage, and in some cases unnecessary downtime.

Below, let’s go through the exact reasons this occurs and how to get it sorted out quickly.

How the Error Looks

The common message appears like this: (virt-manager warning KVM is not available)

TASK ERROR: KVM virtualization configured, but not available. Either disable in VM configuration or enable in BIOS.

Why It Matters

• Virtual Machine Failure: VMs that rely on KVM won’t start.
• Performance Issues: Without KVM, machines fall back to slower emulation.
• Resource Drain: CPU and memory consumption go up.
• Delays: Time lost in troubleshooting can hit operations.

What Causes the Error and How to Resolve It

Virtualisation Disabled in BIOS

This is the most common culprit.

How to resolve it:

• Restart the computer.
• Enter BIOS setup (usually F2, DEL, or ESC at boot).
• Find virtualization settings under Advanced, CPU Configuration, or Security.
• Enable Intel VT-x or AMD-V (often shown as SVM Mode Mode for AMD).
• Save with F10 and exit.

KVM Modules Not Loaded

Sometimes the kernel modules aren’t loaded.

Check with:

lsmod | grep kvm

If no output, load them:

sudo modprobe kvm

sudo modprobe kvm_intel   # For Intel CPUs

sudo modprobe kvm_amd     # For AMD CPUs

Incompatible CPU

Some CPUs don’t support virtualization at all.

Verify with:

egrep '(vmx|svm)' /proc/cpuinfo

If nothing shows up, the CPU lacks support. The only option here is upgrading the processor.

Missing /dev/kvm Device

If /dev/kvm isn’t present, KVM isn’t set up properly.

• First, ensure modules are loaded.
• Check permissions:

ls -l /dev/kvm

• If it’s still missing, reboot after loading the modules.

Incorrect VM Configuration

A VM might be pointing to KVM when it shouldn’t.

Edit the VM config, usually in /etc/libvirt/qemu/, and change:

<domain type='kvm'>

To

<domain type='qemu'>

Then restart the VM.

Outdated BIOS/Firmware

Old BIOS versions often cause problems with virtualization.

• Visit your motherboard vendor’s site.
• Update to the latest BIOS version.
• Recheck Intel VT-x or AMD-V after the update.

Conflicting Hypervisor Software

If VMware or VirtualBox is installed, they may block KVM.

• Make sure no other hypervisors are running.
• Uninstall or disable them if needed.

Kernel Parameters Not Set

Sometimes kernel parameters need to be specified.

Edit GRUB (usually /etc/default/grub) and add:

• For Intel: intel_iommu=on
• For AMD: amd_iommu=on

Then run:

sudo update-grub

Reboot afterwards.

How to Prevent Future Issues

• Keep BIOS firmware up to date.
• After updates, confirm virtualization is still enabled.
• Regularly update kernel and virtualization packages.
• Maintain documentation for system changes.

[If needed, Our team is available 24/7 for additional assistance.]

Conclusion

The error kvm virtualisation configured but not available message is common, but with the right checks in BIOS, kernel modules, and VM configurations, you can eliminate it without much downtime. Always start with BIOS settings, then move to modules and system configs. Once everything is aligned, KVM will work the way it should, delivering efficient virtualization again.