From: Salvatore Bonaccorso <carnil@debian.org>
To: Andrew Wilson <wizlonex@gmail.com>, 1145026-done@bugs.debian.org
Cc: Sean Christopherson <seanjc@google.com>,
ashish.kalra@amd.com, aik@amd.com, herbert@gondor.apana.org.au,
stable@vger.kernel.org, regressions@lists.linux.dev,
thomas.lendacky@amd.com, john.allen@amd.com, davem@davemloft.net,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Bug#1145026: [REGRESSION] [6.12.y] crypto: ccp - Move SEV/SNP Platform initialization to KVM breaks SEV-ES VM launch
Date: Wed, 2 Sep 2026 22:22:45 +0200 [thread overview]
Message-ID: <apiFlWsTBSsdU0jx@eldamar.lan> (raw)
In-Reply-To: <CALAyJWqXT=LFr2wAi4egPPQX57=NRK5tXJh_t4nOKqrJbfga3A@mail.gmail.com>
Source: linux
Source-Version: 6.12.105-1
Hi,
On Wed, Sep 02, 2026 at 03:14:48PM -0400, Andrew Wilson wrote:
> Hi Sean, Salvatore,
>
> Tested-by: Andrew Wilson <your.email@address.com>
>
> (With strong assistance from Gemini guiding me through builds, module
> DKMS rebuilds, and interpreting logs!)
>
> I can confirm that commit 6b748c39d18e completely resolves the issue,
> and SEV, SEV-ES, AND SEV-SNP are fully functional on official Debian
> packages (tested on EPYC Rome and EPYC Milan servers).
>
> Here are the test results from bare-metal hardware:
>
> 1. Upstream v6.12.104 (Source build) on AMD EPYC (Rome):
> * Tested SEV-ES: Functional, VMs launch cleanly.
>
> 2. Debian 6.12.107-1 (linux-image-6.12.107+deb13-amd64) on AMD EPYC (Rome):
> * Tested SEV & SEV-ES: Functional.
> [ 3.676036] kvm_amd: SEV enabled (ASIDs 16 - 253)
> [ 3.690542] kvm_amd: SEV-ES enabled (ASIDs 1 - 15)
> [ 3.735896] ccp 0000:26:00.1: SEV API:0.24 build:22
>
> 3. Debian 6.12.107-1 (linux-image-6.12.107+deb13-amd64) on AMD EPYC (Milan):
> * Tested SEV-SNP: Fully functional!
> * Host log:
> [ 4.678767] kvm_amd: SEV enabled (ASIDs 256 - 509)
> [ 4.684694] kvm_amd: SEV-ES enabled (ASIDs 1 - 255)
> [ 4.690563] kvm_amd: SEV-SNP enabled (ASIDs 1 - 255)
> [ 6.212275] ccp 0000:47:00.1: SEV-SNP API:1.58 build:2
> * Guest dmesg:
> [ 0.908804] Memory Encryption Features active: AMD SEV SEV-ES SEV-SNP
> [ 0.908820] SEV: Status: SEV SEV-ES SEV-SNP
> [ 2.109524] SEV: SNP running at VMPL0.
> [ 3.439649] sev-guest sev-guest: Initialized SEV guest driver
> (using VMPCK0 communication key)
>
> Because Debian builds KVM as a module (CONFIG_KVM_AMD=m), we avoid the
> built-in CONFIG_KVM_AMD=y SNP race on 6.12.y, so both SEV-ES and
> SEV-SNP are completely working out-of-the-box on 6.12.107-1.
>
> Salvatore: Debian bug #1145026 can be marked fully resolved by
> linux-image-6.12.107-1.
Thanks for the confirmation, thanks Sean for checking the report!
On Debian's side I'm thus closing the bugreport.
Regards,
Salvatore
prev parent reply other threads:[~2026-09-02 20:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 16:34 Andrew Wilson
2026-09-02 17:06 ` Sean Christopherson
2026-09-02 19:14 ` Andrew Wilson
2026-09-02 20:22 ` Salvatore Bonaccorso [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=apiFlWsTBSsdU0jx@eldamar.lan \
--to=carnil@debian.org \
--cc=1145026-done@bugs.debian.org \
--cc=aik@amd.com \
--cc=ashish.kalra@amd.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=john.allen@amd.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=seanjc@google.com \
--cc=stable@vger.kernel.org \
--cc=thomas.lendacky@amd.com \
--cc=wizlonex@gmail.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®