Nested kvm on Intel (vmx) unfortunately saw quite a bit of regression starting with kernel v3.10 by commit 5f3d5799974b89100268ba813cec8db7bd0693fb KVM: nVMX: Rework event injection and recovery Then there were several changes to nested VMX until v3.12 where things seemed to work again. Sounds a bit like 3.13 again does something bad. Saucy problems would be bug #1208455 and there is another issue right now with 32bit kvm on Trusty hosts which is tracked as bug #1268906 (just for having references).
We need to see what we can do about Saucy, the problem is that v3.11 sits right in the middle of meddling around with nested VMX. So going back may require as much change as going forward. And either way is a risk (for other regressions). The message about zapping shadow pages looks to be rather some forgotten debug code. Some index is initialized in a way that causes that to happen quite early and is supposed to ensure that case is tested (maybe it still is not, who knows, but should be less likely). >From your description it sounds like some nested VMX (again) but just to make >sure I got this right. The failing combination is: - Host: P user-space, T kernel; Lvl1: P user-space, P kernel; Lvl2: T user-space, T kernel - Host: T user-space, T kernel; Lvl1: T user-space, T kernel; Lvl2: T user-space, T kernel Is that correct or did I get that wrong? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1278531 Title: nested kvm fails with trust and upstream kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1278531/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
