2015-02-19 13:07+0100, Kashyap Chamarthy:
> Just did two tests with 3.18:
> 
> (1) Kernel 3.18 on L0 and 3.20 on L1
> 
>     Result: Booting L2 guest causes L1 to reboot, and the same[*] stack
>             trace on L0 (mentioned on this thread previously).
> 
>             But, annoyingly enough, when I did test (2) below, and then
>             switched back to test (1), I don't notice the said stack
>             trace in L0's `dmesg` however many times I boot an L2 guest.
> 
> (2) Kernel 3.18 on both L0 and L1
> 
>     Result: Booting L2 guest causes L1 to reboot, but *no* stack trace
>             on L0

It is WARN_ON_ONCE, so it quite likely happened with 3.18 too.

5f3d5799974b8 KVM: nVMX: Rework event injection and recovery:
  This concept is based on the rule that a pending vmlaunch/vmresume is
  not canceled. Otherwise, we would risk to lose injected events or leak
  them into the wrong queues. Encode this rule via a WARN_ON_ONCE at the
  entry of nested_vmx_vmexit.

I wonder if we have broken the invariant since 3.9 ...
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to