Re: SEV-ES guest shutdown: linux-next regression with QEMU 10.2.2; smp>1

[Sean Christopherson <seanjc@google.com>]

On Tue, Apr 07, 2026, Srikanth Aithal wrote:
> On 4/1/2026 9:48 PM, Sean Christopherson wrote:
> > > - With older host kernels (< next-20260304) + QEMU 10.2.2 → clean shutdown
> > > (no hang, no termination message, QEMU exits normally).
> > > - With linux-next (next-20260331) + QEMU 10.2.2 → hang at the register dump
> > > after "reboot: Power down"; only Ctrl+C triggers the "SEV-ES guest requested
> > > termination: 0x0:0x0" message.
> > > - With linux-next + QEMU master (or 10.2.2 + cherry-pick of 56d89db2cfd8) →
> > > no hang (the termination is converted to a guest panic instead).
> > 
> > What guest kernel are you using?  Bisecting to that commit for just the *host*
> > kernel is baffling.  I could see it preventing KVM from loading or something, but
> > it should be completely out of scope with respect to guest activity.
> > 
> > How are you initiating shutdown withing the guest?  What's the full QEMU command
> > line?
> > 
> > Can you also provide the OVMF image?  E.g. in case the hang occurs in EFI runtime
> > services or something.
> > 
> > I want to get this sorted out before the merge window and so would prefer not to
> > delay root causing this by a week or more.
> 
> 
> The bisection was actually performed on the guest kernel (not the host).
> Sorry for the confusion.

LOL, that changes things slightly.  I reproduced this on my end (finally built
a new version of OVMF that supports SEV-ES).  I'll take it from here.