qemu-system-x86_64: -device tpm-tis,tpmdev=tpm-tpm0,id=tpm0: Property 'tpm-tis.tpmdev' can't find value 'tpm-tpm0'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
qemu (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
Unassigned | ||
Groovy |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
* TPM isn't always easy, but at least some rough edges can be improved.
In this case some qemu commandlines will lead to odd error reporting
which is a) a false-positive and b) blocking the use case.
* This was fixed upstream and hereby the fix is backported
[Test Case]
Easiest - using passthrough:
You need a system that has a TPM:
$ sudo qemu-system-x86_64 -nodefaults -S -display none -monitor stdio -tpmdev passthrough,
If you enter the qemu monitor you are good, if qemu doesn't start complaining about its command line arguments then the error is still present.
One can (if you want to go the extra mile) also set up a swtpm based emulator and try that. But swtpm isn't in the archive yet and trousers (a dependency) has issues on install. Commands would then be like:
$ swtpm socket --tpmstate dir=/tmp/mytpm1 --ctrl type=unixio,
$ qemu-system-x86_64 -nodefaults -S -display none -monitor stdio -chardev socket,
[Where problems could occur]
* The changes are local only to the tpm code in qemu. So we can assume
that other areas will unlikely be affected, but at the same time errors
would occur in exactly that place. So for the time after release our
bug triage can be extra careful if anyone mentioned qemu+tpm to spot
regressions.
[Other Info]
* n/a
----
Hello. The TPM device in virt-manager never really worked in Ubuntu (I tried upgrades from 16.04 to 20.04 and each of them exhibited a different kind of issues).
The Ubuntu 20.04 versions of libvirt/qemu are throwing the following error:
qemu-system-x86_64: -device tpm-tis,
Our employer changed a security policy, requiring encrypted drives and that endangers usage of Linux as the host system without making the tpm passthrough working.
Versions:
libvirt0:amd64 6.0.0-0ubuntu8.5
qemu-kvm 1:4.2-3ubuntu6.8
virt-manager 1:2.2.1-3ubuntu2.1
Related branches
- Robie Basak: Approve (sru)
- Canonical Server: Pending requested
- git-ubuntu developers: Pending requested
-
Diff: 136 lines (+114/-0)3 files modifieddebian/changelog (+7/-0)
debian/patches/series (+1/-0)
debian/patches/ubuntu/lp-1903864-tpm_emulator-Report-an-error-if-chardev-is-missing.patch (+106/-0)
- Robie Basak: Approve (sru)
- Canonical Server: Pending requested
- Canonical Server packageset reviewers: Pending requested
- git-ubuntu developers: Pending requested
-
Diff: 136 lines (+114/-0)3 files modifieddebian/changelog (+7/-0)
debian/patches/series (+1/-0)
debian/patches/ubuntu/lp-1903864-tpm_emulator-Report-an-error-if-chardev-is-missing.patch (+106/-0)
CVE References
tags: | added: server-next |
description: | updated |
affects: | launchpad → ubuntu-translations |
no longer affects: | ubuntu-translations |
I've tried many different workarounds by editing the /usr/bin/kvm wrapper or even adding custom KVM arguments to /etc/libvirt/ qemu/Win10. xml, but nothing worked for me. The root cause could be in qemu patches. I've found a thread mentioning the above is a regression.