error: unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
qemu-kvm (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
After some update (I really didn't check which one brought this problem), virsh commands started to fail:
helio@machine:KVM$ virsh start node-1
error: Failed to start domain node-1
error: unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
node-1 was a previously defined VM which was working perfectly.
I removed and loaded again the kernel modules kvm and kvm-intel. Then a new error arouse:
helio@machine:KVM$ virsh start node-1
error: Failed to start domain node-1
error: unsupported configuration: guest and host CPU are not compatible: Host CPU does not provide required features: svm
I could track this problem is related to the following bug: https:/
I could fix patching kvm-spice.
root@machine:~# cat /usr/bin/kvm-spice
#!/bin/sh
#exec qemu-system-x86_64 -enable-kvm "$@"
exec qemu-system-x86_64 -machine accel=kvm:tcg -enable-kvm "$@"
Hi,
the "fix"to kvm-spice is not something that is generally applicable.
The bug you linked also states some success with clearing /var/cache/ libvirt/ qemu/capabiliti es/.
The fix itself to avoid parsing -help as a fallback is in libvirt >=v1.2.11 which means >=Vivid releases. It is not in trusty thou.
What version were you on when hitting this issue?