Closed Orotusso closed 1 year ago
When a swtpm daemon is created manually and the appropriate flags passed to QEMU, TPM functionality is restored.
What command line do you use to run swtpm daemon?
swtpm socket --tpm2 --tpmstate dir=/tmp/tmp.XXXXXXX/state --ctrl type=unixio,path=/tmp/tmp.XXXXXXX/swtpm.sock,terminate
The above is what is used for the swtpm process, then disabling the TPM checkmark in appliance settings and passing the flags into QEMU through the options field
Unfortunately, I cannot reproduce this issue.
Unfortunately, I no longer have access to the gns3 environment where this issue is occurring.
Describe the bug When attempting to use TPM on a Windows 11 Enterprise appliance, the QEMU process exists with return code: 1. Swtpm version is 0.8.0, compiled on 20230621 from Github repo. The tmp folder supposedly containing the swtpm socket is empty. When a swtpm daemon is created manually and the appropriate flags passed to QEMU, TPM functionality is restored.
GNS3 version and operating system (please complete the following information):
To Reproduce Steps to reproduce the behavior:
Screenshots or videos