Comment 7 for bug 1329956

For the benefit of the last commenter and anyone else who comes across this ticket:

As determined on the mailing list in June, the bug appears to be with KVM's apicv on processors that support the feature. I haven't heard anything about a fix, but the best workaround is to disable apicv when loading the KVM kernel module, e.g.:

# modprobe kvm_intel enable_apicv=N

You can verify the parameter by checking the contents of /sys/module/kvm_intel/parameters/enable_apicv.