From: Paolo Bonzini <pbonzini@redhat.com>
To: "Aithal, Srikanth" <sraithal@amd.com>,
Sean Christopherson <seanjc@google.com>
Cc: open list <linux-kernel@vger.kernel.org>, KVM <kvm@vger.kernel.org>
Subject: Re: SEV-ES guest shutdown: linux-next regression with QEMU 10.2.2; smp>1
Date: Fri, 20 Mar 2026 17:11:02 +0100 [thread overview]
Message-ID: <415cb64d-0a39-4602-9740-04abf4906b88@redhat.com> (raw)
In-Reply-To: <c820e242-9f3a-4210-b414-19d11b022404@amd.com>
On 3/20/26 17:08, Aithal, Srikanth wrote:
>
> Questions:
>
> KVM: Is the interaction/issue with older QEMU (e.g. v10.2.2) expected
> here, or is there anything that should be adjusted or documented
> following 428afac5a8ea, like for multi-vCPU SEV-ES guests?
No, it's not.
> QEMU: Would a stable backport of 56d89db2cfd8 to 10.2.x (or equivalent
> handling of SEV-ES termination) be appropriate for users staying on
> stable QEMU while moving to newer host kernels?
It's not a commit I was expecting to have any effect in practice, but it
does improve user experience a little bit when things go south in the
kernel, so we could backport it.
Paolo
next prev parent reply other threads:[~2026-03-20 16:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 16:08 Aithal, Srikanth
2026-03-20 16:11 ` Paolo Bonzini [this message]
2026-03-23 13:10 ` Tom Lendacky
2026-04-01 11:24 ` Aithal, Srikanth
2026-04-01 12:53 ` Tom Lendacky
2026-04-01 14:19 ` Aithal, Srikanth
2026-04-01 16:18 ` Sean Christopherson
2026-04-01 17:39 ` Tom Lendacky
2026-04-07 8:51 ` Aithal, Srikanth
2026-04-07 18:21 ` Sean Christopherson
2026-04-07 20:38 ` Sean Christopherson
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=415cb64d-0a39-4602-9740-04abf4906b88@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seanjc@google.com \
--cc=sraithal@amd.com \
/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
all inboxes | Powered by JetHome®