On Fri, Jan 26, 2024 at 2:29 AM Orion Poplawski wrote:
>
> We have various VMs that are back by luks encrypted LVs. At boot the volumes
> are decrypted by clevis. The problem we are seeing at the moment is that the
> VMs are started before the block devices are decrypted. Our current solution
On Fri, Jan 26, 2024 at 1:29 AM Orion Poplawski wrote:
> We have various VMs that are back by luks encrypted LVs. At boot the
> volumes
> are decrypted by clevis. The problem we are seeing at the moment is that
> the
> VMs are started before the block devices are decrypted. Our current
> solut
We have various VMs that are back by luks encrypted LVs. At boot the volumes
are decrypted by clevis. The problem we are seeing at the moment is that the
VMs are started before the block devices are decrypted. Our current solution
is:
# cat /etc/systemd/system/virtqemud.service.d/override.conf
Hi.
I sent below mail some week ago, Barry's reply left me unsure as to
whether this would be a bug or not. I still tend do assume that I'm
"doing something wrong".
So before I open an issue on GitHub, I'll give it another try here.
Thanks.
I'm playing with the LogFilterPatterns= directive on
