From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 218792] New: Guest call trace with mwait enabled
Date: Tue, 30 Apr 2024 07:32:26 +0000 [thread overview]
Message-ID: <bug-218792-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=218792
Bug ID: 218792
Summary: Guest call trace with mwait enabled
Product: Virtualization
Version: unspecified
Hardware: Intel
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: kvm
Assignee: virtualization_kvm@kernel-bugs.osdl.org
Reporter: farrah.chen@intel.com
Regression: No
Environment:
host/guest kernel:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
e67572cd220(v6.9-rc6)
QEMU: https://gitlab.com/qemu-project/qemu.git master 5c6528dce86d
Host/Guest OS: Centos stream9/Ubuntu24.04
Bug detail description:
Boot Guest with mwait enabled(-overcommit cpu-pm=on), guest call trace
"unchecked MSR access error"
Reproduce steps:
img=centos9.qcow2
qemu-system-x86_64 \
-name legacy,debug-threads=on \
-overcommit cpu-pm=on \
-accel kvm -smp 8 -m 8G -cpu host \
-drive file=${img},if=none,id=virtio-disk0 \
-device virtio-blk-pci,drive=virtio-disk0 \
-device virtio-net-pci,netdev=nic0 -netdev
user,id=nic0,hostfwd=tcp::10023-:22 \
-vnc :1 -serial stdio
Guest boot with call trace:
[ 0.475344] unchecked MSR access error: RDMSR from 0xe2 at rIP:
0xffffffffb5a966b8 (native_read_msr+0x8/0x40)
[ 0.476465] Call Trace:
[ 0.476763] <TASK>
[ 0.477027] ? ex_handler_msr+0x128/0x140
[ 0.477460] ? fixup_exception+0x166/0x3c0
[ 0.477934] ? exc_general_protection+0xdc/0x3c0
[ 0.478481] ? asm_exc_general_protection+0x26/0x30
[ 0.479052] ? __pfx_intel_idle_init+0x10/0x10
[ 0.479587] ? native_read_msr+0x8/0x40
[ 0.480057] intel_idle_init_cstates_icpu.constprop.0+0x5e/0x560
[ 0.480747] ? __pfx_intel_idle_init+0x10/0x10
[ 0.481275] intel_idle_init+0x161/0x360
[ 0.481742] do_one_initcall+0x45/0x220
[ 0.482209] do_initcalls+0xac/0x130
[ 0.482643] kernel_init_freeable+0x134/0x1e0
[ 0.483159] ? __pfx_kernel_init+0x10/0x10
[ 0.483648] kernel_init+0x1a/0x1c0
[ 0.484087] ret_from_fork+0x31/0x50
[ 0.484541] ? __pfx_kernel_init+0x10/0x10
[ 0.485030] ret_from_fork_asm+0x1a/0x30
[ 0.485462] </TASK>
--
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:[~2024-04-30 7:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 7:32 bugzilla-daemon [this message]
2024-04-30 11:32 ` [Bug 218792] Guest call trace with mwait enabled bugzilla-daemon
2024-04-30 16:41 ` [Bug 218792] New: " Sean Christopherson
2025-07-31 8:59 ` Chenyi Qiang
2024-04-30 16:42 ` [Bug 218792] " bugzilla-daemon
2024-07-12 8:11 ` bugzilla-daemon
2024-07-12 8:40 ` bugzilla-daemon
2025-07-31 8:59 ` bugzilla-daemon
2025-08-08 21:05 ` bugzilla-daemon
2025-08-08 22:59 ` Sean Christopherson
2025-08-08 22:59 ` 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-218792-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.