On Tue, Jul 31, 2012 at 4:52 PM, Dan Allen <dan.j.allen(a)gmail.com> wrote:
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:
https://bugzilla.redhat.com/show_bug.cgi?id=714271
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.
No, but you don't need 3.4.7. The 3.5 update should already contain
the same patch that fixed the libvirt issue. Specifically:
CPU-hotplug-cpusets-suspend-Dont-modify-cpusets-during.patch
which is definitely applied to the 3.5 F17 update.
josh