Thanks Munzir. For anyone following along, the easiest way to verify is to do
kvm-spice -monitor stdio -vnc :1 and see: QEMU 1.0 monitor - type 'help' for more information (qemu) info kvm kvm support: disabled I agree that ideally for it to be named kvm, it should have kvm enabled by default. That that isn't happening is an unfortunate side-effect of sharing the codebase with the qemu tree in universe. I'm not sure however whether patching the code during build to enable kvm by default would be acceptable or (in terms of long-term maintenance) desirable. While the patch would be simple, it would be almost certain to rot over time and eventually cause a build failure or, worse, a subtler hard-to- diagnose error. Another alternative is to rename kvm-spice to qemu-spice. That in itself seems unfortunate to me, and offhand I"m not sure if that would cause issues with having libvirt call it when qemu-kvm was available. A third possibility is to accept it and leave this as an open, known, bug. So I'm open to input right now about the best path forward. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/902237 Title: kvm-spice is very slow to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-linaro/+bug/902237/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
