From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 217796] latest Zen Inception fixes breaks nested kvm virtualization on AMD
Date: Tue, 15 Aug 2023 17:53:03 +0000 [thread overview]
Message-ID: <bug-217796-28872-jhwONZyvXD@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217796-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=217796
--- Comment #1 from sonst+kernel@o-oberst.de ---
Note, adding spec_rstack_overflow=off as a kernel command line makes nested VM
boot properly again without problems:
https://bugs.archlinux.org/task/79384
So, spec_rstack_overflow=safe-ret is breaking nested KVM virtualization.
--
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 prev parent reply other threads:[~2023-08-15 17:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 14:55 [Bug 217796] New: latest Zen Inception fixes breaks nested kvm virtualization on AMD bugzilla-daemon
2023-08-15 17:53 ` bugzilla-daemon [this message]
2023-08-15 20:30 ` [Bug 217796] " bugzilla-daemon
2023-08-19 10:39 ` 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-217796-28872-jhwONZyvXD@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