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@xxxxxxxxxxxxxxxxxxx wrote: > > https://bugzilla.kernel.org/show_bug.cgi?id=203543 > > > > --- Comment #10 from moi@xxxxxxxxxxxxx --- > > 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?
