When
Hyper-V enlightment
is enabled (whatever it is?) in the advanced config of a kvm guest libvirt logs show an error as follows and VM hangs on boot:
# tail /var/log/libvirt/libvirtd.log
...
x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_spinlocks
Should be named ‘enlightenment’ btw., shouldn’t it?