From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 215964] New: 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 02:45:27 +0000 [thread overview]
Message-ID: <bug-215964-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=215964
Bug ID: 215964
Summary: nVMX: KVM(L0) does not perform a platform reboot when
guest(L2) trigger a reboot event through IO-Port-0xCF9
Product: Virtualization
Version: unspecified
Kernel Version: 5.10+
Hardware: Intel
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: kvm
Assignee: virtualization_kvm@kernel-bugs.osdl.org
Reporter: yadong.qi@intel.com
Regression: No
Background:
We have a lightweight Hypervisor(iKGT) which aims to monitor very limited
resources and passthrough most resources to its guest. The IO-Port:0x3F9 is
also passthrough to its guest, so when guest tries to trigger a reboot
event(through IO-port:0x3F9), the hardware will do the platform reset directly.
We ported it to running under KVM, then it becomes nested virtualization
architecture: KVM(L0), iKGT(L1), Guest(L2).
Reproduce Steps:
Guest(L2) write 0xCF9 to trigger a platform reboot.
Expected result:
KVM perform a virtual platform reset and reboot guest.
Current result:
It seems KVM only reset part of the vCPU(L2), but it does not clear the nVMX
state, it still tries to emulate VMExit to iKGT(L1). We still can observe
VMExit from iKGT(L1) and the exit reason is not expected.
--
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 reply other threads:[~2022-05-10 2:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 2:45 bugzilla-daemon [this message]
2022-05-10 16:01 ` [Bug 215964] nVMX: KVM(L0) does not perform a platform reboot when guest(L2) trigger a reboot event through IO-Port-0xCF9 bugzilla-daemon
2022-05-11 2:29 ` 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@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