On Tue, Mar 04, 2014 at 09:13:40AM +0100, Paolo Bonzini wrote: > Il 04/03/2014 03:40, Ian Pilcher ha scritto: > >Is this a known problem? I just tried using nested vmx for the first > >time since upgrading my system from F19 (3.12.?? at the time) to F20, > >and I cannot start any L2 guests. The L2 guest appears to hang almost > >immediately after starting, consuming 100% of one of the L1 guest's > >VCPUs. > > > >If I reboot with kernel-3.12.10-300.fc20.x86_64, the problem does not > >occur. > > > >Any known workaround? (Other than using 3.12.10?) > > There is a fix on the way to the 3.13 kernel. > > You can open a Fedora bug and ask them to include > http://article.gmane.org/gmane.linux.kernel.stable/82043/raw in the > kernel. Thanks for fixing this. It affects a lot of libguestfs users too. I opened this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1073663 Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://people.redhat.com/~rjones/virt-top -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
