On Fri, Dec 16, 2016 at 10:02:23AM +0100, Christian Ehrhardt wrote: > Package: libvirt > Version: 2.5.0-1 > Severity: normal > > This is a continuation of debbug 848247. > But you said you want to close that with next upload but I should come back. > > While the tests are now working fine in local autopkgtest I was throwing > them at launchpad this night. > And I think there I had a case where the discussion on "virt-host-validate > qemu". > > Maybe we should use it as an early exits as in the lxc case - to detect > incompatible environments. > I've seen this: > + virt-host-validate qemu > QEMU: Checking for hardware virtualization > : PASS > QEMU: Checking if device /dev/kvm exists > : FAIL (Check that the 'kvm-intel' or 'kvm-amd' modules are loaded & the > BIOS has enabled virtualization) > > [...] > > + virsh start sqs > error: Failed to start domain sqs > 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. > > That is IMHO due to only having "isolation-container", but could even > happen in isolaton-machine dependin on the setup.
The fix is to use qemu not kvm in the domain XML in this case. -- Guido
