Hey Christian, thanks for taking a look at this, indeed this is somehow confinement related and I can make it work by removing the apparmor profile for the swtpm snap.
I guess I assumed that this bug was related to that since it had the same exact error message and I definitely remembered doing this setup before only like a month or two ago on Groovy and the swtpm-mvo snap has not been updated in ages so I assumed that updating qemu was to blame. What I actually find now is that it seems actually to be due to https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1849753, since what changed for me to trigger my bug around swtpm and qemu is that I started using VS Code as a snap, and so when I run my qemu commands they are effectively being run from inside a classic snap, and swtpm is a strict snap so it cannot inherit all the FD's that VS code has open. If I run from a normal terminal shell and not from within the VS Code integrated terminal the setup works the same again. So all that is to say that indeed there is no regression here, thanks for the insight that this is confinement related, I should be able to easily work around this for my purposes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903864 Title: qemu-system-x86_64: -device tpm-tis,tpmdev=tpm-tpm0,id=tpm0: Property 'tpm-tis.tpmdev' can't find value 'tpm-tpm0' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1903864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
