Prior to kernel 3.4.7, libvirt was getting pinned to a single CPU after resume (making VMs run painfully slow). This problem is documented thoroughly in this BZ:
This problem is fixed in 3.4.7, which is currently waiting on karma in Fedora 16. However, for Fedora 17, it's 3.5 that's in the queue (with -1 karma). Would it be possible to prepare 3.4.7 for Fedora 17 instead of 3.5 so that we get it sooner? This is really a painful bug.
-Dan
--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597