What were you trying to do that didn't work?

Start a vm with vtpm, check libvirtd/virtqemud log, a warnning about swtpm unsupported feature shows:

2025-02-19 10:38:43.149+0000: 74474: warning : qemuTPMGetSwtpmSetupStateArg:350 : This swtpm version doesn't support explicit locking

What is the impact of this issue to you?

warning msgs in libvirtd log may cause customer complaints. As this warning is mostly harmless, as no concurrent setup should take place on the same state, we could downgrade it to the info level.  Found from RHEL-54325.

Please provide the package NVR for which the bug is seen:

rhel10.0:

libvirt-10.10.0-7.el10.x86_64
swtpm-0.9.0-5.el10.x86_64
libtpms-0.9.6-10.el10.x86_64

rhel9.6:

libvirt-10.10.0-7.el9.x86_64
swtpm-0.8.0-2.el9_4.x86_64
libtpms-0.9.1-4.20211126git1ff6fe1f43.el9.x86_64

How reproducible is this bug?:

100%

Steps to reproduce

0. setup libvirtd log

# vim /etc/libvirt/virtqemud.conf 
log_filters="1:qemu 1:libvirt 4:object 4:json 4:event 1:util"
log_outputs="1:file:/var/log/libvirt/virtqemud.log"
# systemctl restart virtqemud

1. start a vm with vtpm

for example: 

<tpm model="tpm-crb">
  <backend type="emulator" version="2.0"/>
  <alias name="tpm0"/>
</tpm>
# virsh start avocado-vt-vm1 
Domain 'avocado-vt-vm1' started

2. check libvirtd log

#   cat /var/log/libvirt/virtqemud.log|grep qemuTPMGetSwtpmSetupStateArg
2025-02-19 10:38:43.051+0000: 74474: warning : qemuTPMGetSwtpmSetupStateArg:350 : This swtpm version doesn't support explicit locking
2025-02-19 10:38:43.149+0000: 74474: warning : qemuTPMGetSwtpmSetupStateArg:350 : This swtpm version doesn't support explicit locking

Expected results

Actual results