From: Jonathan McDowell <noodles@earth.li>
To: Wilfred Mallawa <wilfred.mallawa@wdc.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"qemu-block@nongnu.org" <qemu-block@nongnu.org>
Subject: Re: NVMe: Add SPDM over the storage transport support
Date: Mon, 23 Feb 2026 09:42:56 +0000 [thread overview]
Message-ID: <aZwhIMzkMgu94JeV@earth.li> (raw)
In-Reply-To: <9fb564e200841e2ee4244f1a848120a928cdf024.camel@wdc.com>
On Sat, Feb 21, 2026 at 01:38:49AM +0000, Wilfred Mallawa wrote:
>On Fri, 2026-02-20 at 17:18 +0000, Jonathan McDowell wrote:
>> On Fri, 3 Oct 2025 21:39:41 +1000, you wrote:
>> > This series extends the existing SPDM support in QEMU to support
>> > the DSP0286 SPDM Storage Transport [1] for NVMe. SPDM Storage
>> > Transport uses the NVMe Admin Security Send/Receive commands, as
>> > such, support for these commands have also been added.
>>
>> > With the addition of a new `spdm-trans` CLI argument for NVMe
>> > controllers, users can specify `spdm_trans=nvme` or
>> > `spdm_trans=doe`. This allows for the selection of the SPDM
>> > transport. The `doe` option is the current default, `nvme` would
>> > select SPDM Storage Transport for the controller, where SPDM
>> > communication happens over the NVMe Admin Security Send/Receive
>> > commands.
>>
>> > Support for DSP0286 already exists in `libspdm` [2] and support for
>> > the QEMU SPDM server is being upstreamed for `spdm-utils` [3]. This
>> > series was tested by using `spdm-utils` as the qemu SPDM server
>> > with SPDM Storage Transport support built with `libspdm` v3.8.0,
>> > and `spdm-utils` also as the SPDM requester.
>> Do you have a pointer to the correct spdm-utils version/branch to use
>> for testing this? I tried wilfred/spdm-storage-v4, which appears to
>> be the latest, but it fails to build, and the footnote in your mail
>> is dangling.
>You should be able to use [1] in the host to setup the response server
>for QEMU. So after cargo build:
>
>```
>$ ./target/debug/spdm_utils --qemu-server --spdm-transport-protocol=storage response
>```
…
>Sorry for missing links and different branches... all of this should be
>upstream soon!
Thanks, the pointer to your add-spdm-storage-upstream-v6 branch is
exactly what I needed to get things working.
root@debian-qemu-efi:~# nvme security-recv /dev/nvme0 --secp=0xe8 --spsp=0x0004 --size=32 --al=32
NVME Security Receive Command Success
0 1 2 3 4 5 6 7 8 9 a b c d e f
0000: 20 00 00 10 00 00 00 00 66 00 00 00 00 00 00 00 "........f......."
0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 "................"
>[1]
>https://github.com/twilfredo/spdm-utils/tree/wilfred/add-spdm-storage-upstream-v6
J.
--
< fivemack> it is bruter-force | .''`. Debian GNU/Linux Developer
than a really really stupid | : :' : Happy to accept PGP signed
elephant [on his Python suduku | `. `' or encrypted mail - RSA
solver] | `- key on the keyservers.
prev parent reply other threads:[~2026-02-23 9:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-03 11:39 [PATCH v8 0/5] NVMe: Add SPDM over the storage transport support Wilfred Mallawa
2025-10-03 11:39 ` [PATCH v8 1/5] spdm-socket: add seperate send/recv functions Wilfred Mallawa
2025-10-03 11:39 ` [PATCH v8 2/5] spdm: add spdm storage transport virtual header Wilfred Mallawa
2025-10-03 11:39 ` [PATCH v8 3/5] hw/nvme: add NVMe Admin Security SPDM support Wilfred Mallawa
2025-10-03 11:39 ` [PATCH v8 4/5] spdm: define SPDM transport enum types Wilfred Mallawa
2025-10-03 11:39 ` [PATCH v8 5/5] hw/nvme: connect SPDM over NVMe Security Send/Recv Wilfred Mallawa
2025-10-07 8:05 ` [PATCH v8 0/5] NVMe: Add SPDM over the storage transport support Klaus Jensen
2025-10-09 2:47 ` Alistair Francis
2026-02-20 17:18 ` Jonathan McDowell
2026-02-21 1:38 ` Wilfred Mallawa
2026-02-23 9:42 ` Jonathan McDowell [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=aZwhIMzkMgu94JeV@earth.li \
--to=noodles@earth.li \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=wilfred.mallawa@wdc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.