On Tue, Mar 04, 2014 at 03:00:22PM +0530, Kashyap Chamarthy wrote: > 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. Err, I missed to read this. Sorry about that. > > > > > >Any known workaround? (Other than using 3.12.10?) > > If you want to try, I made a Fedora Kernel scratch build (i.e. not > official) with fix Paolo pointed to below and this works for me: > > http://koji.fedoraproject.org/koji/taskinfo?taskID=6577700 > > (NOTE: Fedora Scratch build URLs won't last more than 10 days or so) > > > > > 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. > > > > Paolo > > -- > > 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 > > -- > /kashyap -- /kashyap -- 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
