From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 219787] New: Guest's applications crash with EXCEPTION_SINGLE_STEP (0x80000004)
Date: Sun, 16 Feb 2025 09:53:58 +0000 [thread overview]
Message-ID: <bug-219787-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=219787
Bug ID: 219787
Summary: Guest's applications crash with EXCEPTION_SINGLE_STEP
(0x80000004)
Product: Virtualization
Version: unspecified
Hardware: AMD
OS: Linux
Status: NEW
Severity: high
Priority: P3
Component: kvm
Assignee: virtualization_kvm@kernel-bugs.osdl.org
Reporter: rangemachine@gmail.com
Regression: No
Created attachment 307665
--> https://bugzilla.kernel.org/attachment.cgi?id=307665&action=edit
Debugger attached to Steam.exe
Overview
========
Linux 6.13 update introduced problem with Windows guest's applications on AMD
processors. Several applications crash with EXCEPTION_SINGLE_STEP (0x80000004).
The list of confirmed software: CrystalDiskMark, Visual Studio Code, Steam,
Looking Glass server, Windows Tweaker.
It never happened prior 6.13 update. I also checked 6.13.3rc and 6.14.1rc
updates, problem persists there too. I did quick check differences in KVM/SVM
between 6.12 and 6.13 and did not found anything that could set trapflag, so
problem could be somewhere deeper inside kernel.
Steps to reproduce
==================
Run VM with Windows guest, launch any software from the list.
Hardware
========
CPU: AMD Ryzen 7 9800X3D (16) @ 5.27 GHz
MB: TUF GAMING X870-PLUS WIFI
Additional Information
======================
Steam crashes when downloading game, Looking Glass crashes on WinAPI
QueryPerformanceCountrer call. Tested on Window 11 22H2/23H2/24H2.
--
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-02-16 9:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-16 9:53 bugzilla-daemon [this message]
2025-02-16 9:54 ` [Bug 219787] Guest's applications crash with EXCEPTION_SINGLE_STEP (0x80000004) bugzilla-daemon
2025-02-16 10:01 ` bugzilla-daemon
2025-02-20 0:31 ` bugzilla-daemon
2025-02-20 2:57 ` bugzilla-daemon
2025-02-20 17:40 ` Sean Christopherson
2025-02-20 7:10 ` bugzilla-daemon
2025-02-20 17:43 ` Sean Christopherson
2025-02-20 17:41 ` bugzilla-daemon
2025-02-20 17:43 ` bugzilla-daemon
2025-02-20 17:46 ` bugzilla-daemon
2025-02-20 19:00 ` bugzilla-daemon
2025-02-21 1:31 ` bugzilla-daemon
2025-02-21 1:31 ` bugzilla-daemon
2025-02-21 1:32 ` bugzilla-daemon
2025-02-21 10:48 ` bugzilla-daemon
2025-02-21 18:22 ` bugzilla-daemon
2025-02-21 18:22 ` bugzilla-daemon
2025-02-21 20:04 ` bugzilla-daemon
2025-02-23 4:57 ` bugzilla-daemon
2025-02-24 11:33 ` bugzilla-daemon
2025-02-24 11:36 ` bugzilla-daemon
2025-06-27 13:19 ` bugzilla-daemon
2025-06-30 12:00 ` bugzilla-daemon
2025-07-02 9:05 ` bugzilla-daemon
2025-07-06 7:00 ` 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-219787-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;
as well as URLs for NNTP newsgroup(s).