Comment 3 for bug 1961531

As of today (2a52fad2d0f92b1a3b93c on stable/xena), this problem still persists. If a user adds the following to their nova-compute.conf (per openstack docs):
```
swtpm_enabled = true

```
it will blow up nova because the compute and libvirt containers do not have an swtpm binary/configs and will crash incessantly. If they also have (say NFS) mounts inside of them, they will remount that NFS path without unmounting it first until they overflow or hit the max mounts limit.

Since i filed this issue, it has become more pressing with newer OS demanding TPMs to work correctly proliferating in the market.

While there is no CVE assigned to this concern, it does create a full-fledged denial of service and due to the kernel stalls from the repeated remounts, may result in loss of or damage to data/systems.