From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 220631] New: kernel crash in kvm_intel module on Xeon Silver 4314s
Date: Mon, 06 Oct 2025 08:44:55 +0000 [thread overview]
Message-ID: <bug-220631-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=220631
URL: https://bugzilla.proxmox.com/show_bug.cgi?id=6767
Bug ID: 220631
Summary: kernel crash in kvm_intel module on Xeon Silver 4314s
Product: Virtualization
Version: unspecified
Hardware: Intel
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: kvm
Assignee: virtualization_kvm@kernel-bugs.osdl.org
Reporter: f.gruenbichler@proxmox.com
Regression: No
Created attachment 308754
--> https://bugzilla.kernel.org/attachment.cgi?id=308754&action=edit
Qemu commandline
one of our users reports a crash in kvm_intel with Windows guests and live
migration. the source and target hosts are identical hardware, kernel version
and bios version wise:
- Supermicro SYS-120C-TN10R servers with Xeon Silver 4314s
- microcode : 0xd000404
- 6.14.8-2-pve (based on Ubuntu 6.14.0-26.26 and upstream stable 6.14.
- guest OS: Windows 11 24H2
the Qemu commandline and dmesg output is attached, the user is CCed to this
bug. unfortunately, we don't have the hardware to reproduce and bisect
ourselves.
this is likely a regression, since the user reports running into the issue
since upgrading to PVE 9, which means switching from kernel 6.8.x to 6.14.x
--
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:[~2025-10-06 8:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-06 8:44 bugzilla-daemon [this message]
2025-10-06 8:46 ` [Bug 220631] kernel crash in kvm_intel module on Xeon Silver 4314s bugzilla-daemon
2025-10-06 11:45 ` bugzilla-daemon
2025-10-06 12:05 ` bugzilla-daemon
2025-10-06 14:26 ` bugzilla-daemon
2025-10-07 1:21 ` bugzilla-daemon
2025-10-08 6:23 ` 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-220631-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