| 2017-11-06 14:47:02 |
Christian Ehrhardt |
description |
Not sure this is an issue yet or a problem with my test setup I have seen this.
But worth to document and trace down at sometime.
On Artful I have seen:
Setting up libvirt-daemon-system (3.6.0-1ubuntu6) ...
virtlockd.service is a disabled or a static unit, not starting it.
Matching that:
$ sudo systemctl status virtlockd --no-pager
● virtlockd.service - Virtual machine lock manager
Loaded: loaded (/lib/systemd/system/virtlockd.service; indirect; vendor preset: enabled)
Active: inactive (dead)
Docs: man:virtlockd(8)
http://libvirt.org
As I said it might be my test env, but that should be checked in more detail as soon as time permits. |
virtlockd has no defaults file installed /etc/default/virtlockd
This was partially fixed in my contrib to Debian, but our removal of the related sysv script rendered it non-working again (Debian didn't have that for some time so they are broken as well).
Note:
I also evaluated that it is correct that the service isn't started after install - that is ok (socket activated, details see below). |
|
