From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 203543] Starting with kernel 5.1.0-rc6, kvm_intel can no longer be loaded in nested kvm/guests
Date: Tue, 21 May 2019 14:18:10 +0000 [thread overview]
Message-ID: <bug-203543-28872-8NTwF5tNJS@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-203543-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=203543
--- Comment #12 from Sean Christopherson (sean.j.christopherson@intel.com) ---
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.
Any chance the successful test used a different command line or something?
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2019-05-21 14:18 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 20:45 [Bug 203543] New: Starting with kernel 5.1.0-rc6, kvm_intel can no longer be loaded in nested kvm/guests bugzilla-daemon
2019-05-07 23:23 ` Liran Alon
2019-05-07 23:29 ` [Bug 203543] " bugzilla-daemon
2019-05-08 4:08 ` bugzilla-daemon
2019-05-08 12:44 ` bugzilla-daemon
2019-05-08 12:46 ` bugzilla-daemon
2019-05-08 13:51 ` bugzilla-daemon
2019-05-08 16:00 ` Liran Alon
2019-05-08 16:21 ` Sean Christopherson
2019-05-08 16:10 ` bugzilla-daemon
2019-05-08 16:29 ` bugzilla-daemon
2019-05-08 22:14 ` bugzilla-daemon
2019-05-21 12:57 ` David Hill
2019-05-21 12:57 ` bugzilla-daemon
2019-05-21 13:37 ` bugzilla-daemon
2019-05-21 14:11 ` Sean Christopherson
2019-05-21 14:17 ` Sean Christopherson
2019-05-21 14:17 ` bugzilla-daemon
2019-05-21 14:18 ` bugzilla-daemon [this message]
2019-05-21 16:02 ` bugzilla-daemon
2019-05-21 18:06 ` bugzilla-daemon
2019-05-26 12:11 ` David Hill
2019-05-26 12:11 ` bugzilla-daemon
2019-12-01 18:07 ` bugzilla-daemon
2019-12-01 21:49 ` bugzilla-daemon
2019-12-02 3:20 ` bugzilla-daemon
2019-12-02 3:42 ` bugzilla-daemon
2019-12-02 4:15 ` bugzilla-daemon
2019-12-02 4:27 ` bugzilla-daemon
2019-12-02 4:44 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-203543-28872-8NTwF5tNJS@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).