On 17/02/2015 12:24, Kashyap Chamarthy wrote: > Afraid, I didn't bisect it, but I just wanted to note that the above > specific WARN was introduced in the above commit. > > I'm sure this Kernel (on L0) does not exhibit the problem: > kernel-3.17.4-301.fc21.x86_64. But, if I had either of these two Kernels > on the physical host, then the said problem manifests (L1 reboots): > 3.19.0-1.fc22 or kernel-3.20.0-0.rc0.git5.1.fc23
Nested APICv is not part of 3.19, so it cannot be the culprit. Can you try 3.18? Paolo -- 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
