How do I check whether a dedicated server supports hardware virtualization?
A CPU virtualization feature is one prerequisite for a hypervisor, not confirmation that the complete host is ready. On x86 systems, Intel VT-x or AMD-V must be available and enabled through the platform’s supported firmware settings. Device passthrough adds separate IOMMU requirements, while ARM platforms have their own supported hardware and software combinations.
Before you start
- Access to the physical host OS; libvirt validation tools for the optional QEMU check.
Instructions
1. Inspect the bare-metal CPU view
Run this on the dedicated host, not inside an existing virtual machine. Record the architecture, model and any virtualization field.
lscpuA reported feature describes what this environment exposes. Compare the exact processor and firmware configuration with the chosen hypervisor’s requirements.
2. Validate the intended Linux virtualization stack
For a Linux host with libvirt’s validation tool installed, use the QEMU-specific check. Read each warning in context rather than treating one CPU flag as a complete readiness result.
sudo virt-host-validate qemuThis inspects host prerequisites. Missing device access, disabled firmware features or unavailable kernel support need different remedies.
Check the result
- The selected hypervisor supports the architecture, required firmware features are enabled, and relevant host validation checks pass before guests are deployed.
Troubleshooting
- A CPU feature is advertised but KVM is unavailable
- Check firmware settings, kernel support and /dev/kvm access. A reboot may be needed after an approved firmware change.
- The command runs inside a guest
- It reports the guest’s exposed capabilities; obtain the bare-metal host inventory for dedicated-hardware verification.
Official references
Use the documentation for your installed version when a flag, service name or platform feature differs.