From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 219009] Random host reboots on Ryzen 7000/8000 using nested VMs (vls suspected)
Date: Thu, 06 Mar 2025 22:19:36 +0000 [thread overview]
Message-ID: <bug-219009-28872-rbhCxN7gDl@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219009-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219009
--- Comment #51 from h4ck3r (h4ck3re404@gmail.com) ---
I finally had time to test differences more clearly.
Cpus i used were 7700x and 9700x
Guest os is windows (linux didn't had most issues in the first place)
No nested virt warning with wsl still persists (probably windows being windows
cause zen5 only guests don't have it)
Pcie "slowdown" is gone using zen5 (no performance penalty on gpu)
No issues with nvme drive passthrough (it would behave as broken hdd on zen4
having huge latency and increased temps for some reason - probably irq
handling)
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2025-03-06 22:19 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-06 11:20 [Bug 219009] New: Random host reboots on Ryzen 7000/8000 using nested VMs (vls suspected) bugzilla-daemon
2024-08-03 14:59 ` [Bug 219009] " bugzilla-daemon
2024-08-23 7:36 ` bugzilla-daemon
2024-08-23 7:37 ` bugzilla-daemon
2024-08-23 20:45 ` bugzilla-daemon
2024-08-23 20:49 ` bugzilla-daemon
2024-08-23 21:08 ` bugzilla-daemon
2024-08-25 11:44 ` bugzilla-daemon
2024-08-25 11:45 ` bugzilla-daemon
2024-08-26 0:07 ` bugzilla-daemon
2024-08-26 0:08 ` bugzilla-daemon
2024-08-27 18:16 ` bugzilla-daemon
2024-08-27 18:19 ` bugzilla-daemon
2024-08-31 0:10 ` bugzilla-daemon
2024-08-31 11:51 ` bugzilla-daemon
2024-08-31 18:58 ` bugzilla-daemon
2024-08-31 21:51 ` bugzilla-daemon
2024-08-31 22:54 ` bugzilla-daemon
2024-10-02 22:52 ` bugzilla-daemon
2024-10-02 22:53 ` bugzilla-daemon
2024-10-02 22:53 ` bugzilla-daemon
2024-10-03 15:03 ` bugzilla-daemon
2024-10-03 15:05 ` bugzilla-daemon
2024-10-03 15:11 ` [Bug 219009] New: " Maxim Levitsky
2024-10-03 15:11 ` [Bug 219009] " bugzilla-daemon
2024-10-03 17:13 ` bugzilla-daemon
2024-10-08 17:32 ` bugzilla-daemon
2024-10-08 17:43 ` bugzilla-daemon
2024-10-08 17:53 ` bugzilla-daemon
2024-10-08 18:26 ` bugzilla-daemon
2024-10-08 19:05 ` bugzilla-daemon
2024-10-08 19:11 ` bugzilla-daemon
2024-10-08 21:35 ` bugzilla-daemon
2024-10-16 13:33 ` bugzilla-daemon
2024-10-16 18:04 ` bugzilla-daemon
2024-10-18 9:53 ` bugzilla-daemon
2024-10-18 19:03 ` bugzilla-daemon
2024-10-21 9:43 ` bugzilla-daemon
2024-10-24 14:37 ` bugzilla-daemon
2024-11-05 17:22 ` bugzilla-daemon
2024-11-18 16:22 ` bugzilla-daemon
2024-11-18 16:48 ` bugzilla-daemon
2024-11-20 19:36 ` bugzilla-daemon
2024-11-20 19:37 ` bugzilla-daemon
2024-11-20 19:39 ` bugzilla-daemon
2024-11-23 1:06 ` bugzilla-daemon
2025-02-21 2:00 ` bugzilla-daemon
2025-02-21 19:45 ` bugzilla-daemon
2025-02-26 1:08 ` bugzilla-daemon
2025-02-26 1:10 ` bugzilla-daemon
2025-02-26 9:50 ` bugzilla-daemon
2025-02-27 13:26 ` bugzilla-daemon
2025-03-06 22:19 ` bugzilla-daemon [this message]
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-219009-28872-rbhCxN7gDl@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