Some firmwares provide a virtual (emulated) TPM device to the guest.
Add a corresponding "vtpm" item to the FirmwareFeature enum to reflect
that.

Signed-off-by: Oliver Steffen <osteffen@redhat.com>
---
 docs/interop/firmware.json | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/docs/interop/firmware.json b/docs/interop/firmware.json
index da0362a2c0..12eb1fd79c 100644
--- a/docs/interop/firmware.json
+++ b/docs/interop/firmware.json
@@ -222,6 +222,8 @@
 #     loading the firmware into flash the 'stateless' setup should be
 #     used.  It is recommened to load the firmware into memory though.
 #
+# @vtpm: The firmware provides a virtual TPM device.
+#
 # Since: 3.0
 ##
 { 'enum' : 'FirmwareFeature',
@@ -230,7 +232,7 @@
              'intel-tdx',
              'enrolled-keys', 'requires-smm',
              'secure-boot', 'host-uefi-vars',
-             'verbose-dynamic', 'verbose-static' ] }
+             'verbose-dynamic', 'verbose-static', 'vtpm' ] }
 
 ##
 # @FirmwareFormat:
-- 
2.52.0

On Fri, Jan 23, 2026 at 09:32:02AM +0100, Oliver Steffen wrote:
> Some firmwares provide a virtual (emulated) TPM device to the guest.
> Add a corresponding "vtpm" item to the FirmwareFeature enum to reflect
> that.

I'm wondering whenever it makes sense to be more specific here, i.e.
pick 'svsm-vtpm' as name, or even 'svsm-vtpm-ephemeral'.  Specifically
because a (future) vtpm with persistence has some additional
requirements such as some storage device for svsm, so libvirt needs to
know those details ...

take care,
  Gerd