On Tue, Jul 31, 2012 at 4:52 PM, Dan Allen <dan.j.allen@xxxxxxxxx> wrote:
> Prior to kernel 3.4.7, libvirt was getting pinned to a single CPU afterNo, but you don't need 3.4.7. The 3.5 update should already contain
> 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.
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.
Oops, misunderstood your response the first time.
Yes, I agree the 3.5 update will have the same fix. I suggested 3.4.6-3 so that we can get the fix sooner since 3.5 seems to be stuck (due to a problem with cinnamon, according to the CI report).
(I am still seeing the issue with 3.4.6-2, which is what we would expect).
-Dan
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in ActionRegistered Linux User #231597
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
