[Pkg-libvirt-maintainers] Bug#1082939: /usr/bin/deb-systemd-helper: error: unable to read virtlockd.socket

[Andrea Bolognani]

On Fri, Oct 04, 2024 at 09:10:45PM +0200, Christoph Anton Mitterer wrote:
> It would additionally be nice know *what exactly* virtlogd/virtlockd
> are needed for (and thus, whether one really needs it or not)... so
> far, I seem to run fine without virtlockd (which I haven't installed,
> after it was split out).

virtlogd is used to handle the output generated by the QEMU process.
Having this as a separate process means that libvirtd can be
restarted without affecting running VMs.

Technically speaking it's only a hard dependency of the QEMU driver,
but until we have split daemons (coming to Debian at some point) it
has to be dragged in unconditionally.

virtlockd is used for storage locking; it's one of two such solutions
implemented in libvirt, the other being sanlock. Most deployments
don't need this, and it's turned off by default. It's safe to leave
it out unless you know that you need it.

-- 
Andrea Bolognani <eof at kiyuko.org>
Resistance is futile, you will be garbage collected.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-libvirt-maintainers/attachments/20241005/80b6572d/attachment.sig>