From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 215964] nVMX: KVM(L0) does not perform a platform reboot when guest(L2) trigger a reboot event through IO-Port-0xCF9
Date: Tue, 10 May 2022 16:01:13 +0000 [thread overview]
Message-ID: <bug-215964-28872-8EZayedt6Z@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215964-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215964
Sean Christopherson (seanjc@google.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |seanjc@google.com
--- Comment #1 from Sean Christopherson (seanjc@google.com) ---
Hmm, so KVM doesn't perform the RESET, that's handled by userspace. KVM's
responsibility is purely to determine whether the OUT 0xCF9 should be forwarded
to L1 or bounced out to userspace.
Does the 0xCF9 I/O access get sent to userspace? If not, can you provide L1's
VMCS configuration for L2? Specifically, the settings for USE_IO_BITMAPS and
the relevant bitmap bits if in use, or UNCOND_IO_EXITING if not using bitmaps.
If the I/O access does show up in userspace, then it's likely a userspace bug,
e.g. userspace fails to clear nested state when emulating RESET.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2022-05-10 16:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 2:45 [Bug 215964] New: nVMX: KVM(L0) does not perform a platform reboot when guest(L2) trigger a reboot event through IO-Port-0xCF9 bugzilla-daemon
2022-05-10 16:01 ` bugzilla-daemon [this message]
2022-05-11 2:29 ` [Bug 215964] " bugzilla-daemon
2022-05-11 13:55 ` bugzilla-daemon
2022-05-12 1:36 ` bugzilla-daemon
2022-05-12 14:06 ` bugzilla-daemon
2022-05-13 1:50 ` bugzilla-daemon
2023-01-26 10:03 ` 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-215964-28872-8EZayedt6Z@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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