From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 219009] New: Random host reboots on Ryzen 7000/8000 using nested VMs (vls suspected)
Date: Sat, 06 Jul 2024 11:20:39 +0000 [thread overview]
Message-ID: <bug-219009-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=219009
Bug ID: 219009
Summary: Random host reboots on Ryzen 7000/8000 using nested
VMs (vls suspected)
Product: Virtualization
Version: unspecified
Hardware: AMD
OS: Linux
Status: NEW
Severity: high
Priority: P3
Component: kvm
Assignee: virtualization_kvm@kernel-bugs.osdl.org
Reporter: zaltys@natrix.lt
Regression: No
Running nested VMs on AMD Ryzen 7000/8000 (ZEN4) CPUs results in random host's
reboots.
There is no kernel panic, no log entries, no relevant output to serial console.
It is as if platform is simply hard reset. It seems time to reproduce it varies
from system to system and can be dependent on workload and even specific CPU
model.
I can reproduce it with kernel 6.9.7 and qemu 9.0 on Ryzen 7950X3D under one
hour by using KVM -> Windows 10/11 with Hyper-V services on or KVM -> Windows
10/11 with 3 VBox VMs (also Win11) running. Others people had it repeatedly
reproduced on Ryzen 7700,7600 and 8700GE, including KVM -> KVM -> Linux.[1] I
also have seen Hetzner (company offering Ryzen based dedicated servers)
customers complaining about similiar random reboots.
I tried looking up errata for Ryzen 7000/8000, but could not find one
published, so I decided to check errata for EPYC 9004 [2], which is also Zen4
arch as Ryzen 7000/8000. It has nesting related bug #1495 (on page 49), which
mentions using Virtualized VMLOAD/VMSAVE can result in MCE and/or system reset.
Based on that errata mentioned above, I reconfigured my system with
kvm_amd.vls=0 and for me random reboots with nested virtualization stopped.
Same was reported by several people from [1].
Somebody from AMD must be asked to confirm if it is really Ryzen 7000/8000
hardware bug, and if there is a better fix than disabling VLS as it has
performance hit. If disabling it is the only fix, then kvm_amd.vls=0 must be
default for Ryzen 7000/8000.
[1]
https://www.reddit.com/r/Proxmox/comments/1cym3pl/nested_virtualization_crashing_ryzen_7000_series/
[2]
https://www.amd.com/content/dam/amd/en/documents/processor-tech-docs/revision-guides/57095-PUB_1_01.pdf
--
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-07-06 11:20 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-06 11:20 bugzilla-daemon [this message]
2024-08-03 14:59 ` [Bug 219009] Random host reboots on Ryzen 7000/8000 using nested VMs (vls suspected) 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
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@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