From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.5 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 56BA9C04AAF for ; Tue, 21 May 2019 14:17:33 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 35EF6217D8 for ; Tue, 21 May 2019 14:17:33 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728296AbfEUORc (ORCPT ); Tue, 21 May 2019 10:17:32 -0400 Received: from mga09.intel.com ([134.134.136.24]:18769 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726750AbfEUORb (ORCPT ); Tue, 21 May 2019 10:17:31 -0400 X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from orsmga004.jf.intel.com ([10.7.209.38]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 21 May 2019 07:17:31 -0700 X-ExtLoop1: 1 Received: from sjchrist-coffee.jf.intel.com (HELO linux.intel.com) ([10.54.74.36]) by orsmga004.jf.intel.com with ESMTP; 21 May 2019 07:17:31 -0700 Date: Tue, 21 May 2019 07:17:31 -0700 From: Sean Christopherson To: bugzilla-daemon@bugzilla.kernel.org Cc: kvm@vger.kernel.org Subject: Re: [Bug 203543] Starting with kernel 5.1.0-rc6, kvm_intel can no longer be loaded in nested kvm/guests Message-ID: <20190521141731.GC22089@linux.intel.com> References: <20190521141101.GB22089@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190521141101.GB22089@linux.intel.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: kvm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org On Tue, May 21, 2019 at 07:11:01AM -0700, Sean Christopherson wrote: > On Tue, May 21, 2019 at 01:37:42PM +0000, bugzilla-daemon@bugzilla.kernel.org wrote: > > https://bugzilla.kernel.org/show_bug.cgi?id=203543 > > > > --- Comment #10 from moi@davidchill.ca --- > > Reverting both commits solves this problem: > > > > f93f7ede087f2edcc18e4b02310df5749a6b5a61 > > e51bfdb68725dc052d16241ace40ea3140f938aa > > Hmm, that makes no sense, f93f7ede087f is a straight revert of > e51bfdb68725. I do see the same behavior on v5.2-rc1 where hiding the > pmu from L1 breaks nested virtualization, but manually reverting both > commits doesn't change that for me, i.e. there's another bug lurking, > which I'll start hunting. Scratch that, had a brain fart and tested the wrong kernel. I do *NOT* see breakage on v5.2-rc1, at least when running v5.2-rc1 as L1 and probing KVM in L2. When running v5.2-rc1 as L0, what are the values of MSRs 0x482 and 0x48e in L1? > > Any chance the successful test used a different command line or something?