swtpm has its own log directory, and it's hardcoded in libvirt[1].
For the records, this location is currently set to:
/var/log/swtpm/libvirt/qemu
In order to keep some kind of consistency with the current log structure
in /var/log/containers/libvirt, we will keep the "qemu" subdirectory -
it already exists for other qemu-related services, therefore it makes
sense to keep that subdirectory.
This is possible since the swtpm log filename is composed of the
instance ID suffixed by "-swtpm.log", leading to a clear view.
Reviewed: https:/ /review. opendev. org/c/openstack /puppet- tripleo/ +/812430 /opendev. org/openstack/ puppet- tripleo/ commit/ a4750e1660a22de 0605d9fc46546ac a78fa49824
Committed: https:/
Submitter: "Zuul (22348)"
Branch: stable/wallaby
commit a4750e1660a22de 0605d9fc46546ac a78fa49824
Author: Cédric Jeanneret <email address hidden>
Date: Mon Sep 27 11:47:51 2021 +0200
Add a new bind-mount for vTPM logs
swtpm has its own log directory, and it's hardcoded in libvirt[1]. log/swtpm/ libvirt/ qemu
For the records, this location is currently set to:
/var/
In order to keep some kind of consistency with the current log structure containers/ libvirt, we will keep the "qemu" subdirectory -
in /var/log/
it already exists for other qemu-related services, therefore it makes
sense to keep that subdirectory.
This is possible since the swtpm log filename is composed of the
instance ID suffixed by "-swtpm.log", leading to a clear view.
[1] https:/ /gitlab. com/libvirt/ libvirt/ -/commit/ f9cd29a2e44d61d a0fc94f245d2720 6ea66e1161
Related: rhbz#2007314 b4ef31520439ded 8a08ce50c96 8e2e35e29f2511d ce9de34457)
Related-Bug: #1902468
Change-Id: Ibc80621a622a4e
(cherry picked from commit 98af2c581bce922