From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [nVMX] With 3.20.0-0.rc0.git5.1 on L0, booting L2 guest results in L1 *rebooting* Date: Wed, 18 Feb 2015 17:42:37 +0100 Message-ID: <54E4C0FD.4090906@redhat.com> References: <20150216204013.GI21838@tesla.redhat.com> <54E2D966.9070706@siemens.com> <20150217112426.GL21838@tesla.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org, dgilbert@redhat.com To: Kashyap Chamarthy , Jan Kiszka Return-path: Received: from mail-wi0-f173.google.com ([209.85.212.173]:58887 "EHLO mail-wi0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751245AbbBRQml (ORCPT ); Wed, 18 Feb 2015 11:42:41 -0500 Received: by mail-wi0-f173.google.com with SMTP id bs8so42330235wib.0 for ; Wed, 18 Feb 2015 08:42:40 -0800 (PST) In-Reply-To: <20150217112426.GL21838@tesla.redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: 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