I wanted to check if this is more virt-manager or libvirt to call it badly (or call it in a bad environment).
I spawned a default libvirt based guest with uvtool. In there I then added the most common pattern of
<devices> <tpm model='tpm-tis'> <backend type='emulator' version='2.0'/> </tpm> </devices>
This is showing kind of the same behavior. So while most tests before were about using it directly and together with qemu but self-spawned it seems that at least in the current combination it is the way libvirt uses it that breaks the tool.
I wanted to check if this is more virt-manager or libvirt to call it badly (or call it in a bad environment).
I spawned a default libvirt based guest with uvtool.
In there I then added the most common pattern of
<devices>
<tpm model='tpm-tis'>
<backend type='emulator' version='2.0'/>
</tpm>
</devices>
This is showing kind of the same behavior.
So while most tests before were about using it directly and together with qemu but self-spawned it seems that at least in the current combination it is the way libvirt uses it that breaks the tool.