External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2025-02-06 20:00:05 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: Do not support non-socket activated modular daemons with systemd

Browse Source 
Due to the setup of the modular daemon service files the reverting to non-socket
activated daemons could have never worked.  The reason is that masking the
socket files prevents starting the daemons since they require (as in Requires=
rather than Wants= in the service file) the sockets.  On top of that it creates
issues with some libvirt-guests setups and needlessly increases our support
matrix.

Nothing prevents users to modify their setup in a way that will still work
without socket activation, but supporting such setup only creates burden on our
part.

This technically reverts most of commit 59d30adacd1d except the change made to
the libvirtd manpage since the monolithic daemon still supports traditional mode
of starting even on systemd.

Signed-off-by: Martin Kletzander <mkletzan@redhat.com>
This commit is contained in:
Martin Kletzander 2022-10-18 14:15:38 +02:00
parent 8c9e3dae14
commit f53988d657
12 changed files with 137 additions and 218 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
docs/manpages/virtinterfaced.rst
View File

@ -39,26 +39,25 @@ during startup. None the less it is recommended to avoid restarting with
running guests whenever practical.
SYSTEM SOCKET ACTIVATION
========================
DAEMON STARTUP MODES
====================
The ``virtinterfaced`` daemon is capable of starting in two modes.
In the traditional mode, it will create and listen on UNIX sockets itself.
In socket activation mode, it will rely on systemd to create and listen
on the UNIX sockets and pass them as pre-opened file descriptors. In this
mode most of the socket related config options in
Socket activation mode
----------------------
On hosts with systemd it is started in socket activation mode and it will rely
on systemd to create and listen on the UNIX sockets and pass them as pre-opened
file descriptors. In this mode most of the socket related config options in
``/etc/libvirt/virtinterfaced.conf`` will no longer have any effect.
Socket activation mode is generally the default when running on a host
OS that uses systemd. To revert to the traditional mode, all the socket
unit files must be masked:
::
Traditional service mode
------------------------
$ systemctl mask virtinterfaced.socket virtinterfaced-ro.socket \
virtinterfaced-admin.socket
On hosts without systemd, it will create and listen on UNIX sockets itself.
OPTIONS

37
docs/manpages/virtlxcd.rst
View File

@ -39,40 +39,25 @@ during startup. None the less it is recommended to avoid restarting with
running guests whenever practical.
SYSTEM SOCKET ACTIVATION
========================
DAEMON STARTUP MODES
====================
The ``virtlxcd`` daemon is capable of starting in two modes.
In the traditional mode, it will create and listen on UNIX sockets itself.
In socket activation mode, it will rely on systemd to create and listen
on the UNIX sockets and pass them as pre-opened file descriptors. In this
mode most of the socket related config options in
Socket activation mode
----------------------
On hosts with systemd it is started in socket activation mode and it will rely
on systemd to create and listen on the UNIX sockets and pass them as pre-opened
file descriptors. In this mode most of the socket related config options in
``/etc/libvirt/virtlxcd.conf`` will no longer have any effect.
Socket activation mode is generally the default when running on a host
OS that uses systemd. To revert to the traditional mode, all the socket
unit files must be masked:
::
Traditional service mode
------------------------
$ systemctl mask virtlxcd.socket virtlxcd-ro.socket \
virtlxcd-admin.socket
If using libvirt-guests service then the ordering for that service needs to be
adapted so that it is ordered after the service unit instead of the socket unit.
Since dependencies and ordering cannot be changed with drop-in overrides, the
whole libvirt-guests unit file needs to be changed. In order to preserve such
change copy the installed ``/usr/lib/systemd/system/libvirt-guests.service`` to
``/etc/systemd/system/libvirt-guests.service`` and make the change there,
specifically make sure the ``After=`` ordering mentions ``virtlxcd.service`` and
not ``virtlxcd.socket``:
::
[Unit]
After=virtlxcd.service
On hosts without systemd, it will create and listen on UNIX sockets itself.
OPTIONS

23
docs/manpages/virtnetworkd.rst
View File

@ -39,26 +39,25 @@ during startup. None the less it is recommended to avoid restarting with
running guests whenever practical.
SYSTEM SOCKET ACTIVATION
========================
DAEMON STARTUP MODES
====================
The ``virtnetworkd`` daemon is capable of starting in two modes.
In the traditional mode, it will create and listen on UNIX sockets itself.
In socket activation mode, it will rely on systemd to create and listen
on the UNIX sockets and pass them as pre-opened file descriptors. In this
mode most of the socket related config options in
Socket activation mode
----------------------
On hosts with systemd it is started in socket activation mode and it will rely
on systemd to create and listen on the UNIX sockets and pass them as pre-opened
file descriptors. In this mode most of the socket related config options in
``/etc/libvirt/virtnetworkd.conf`` will no longer have any effect.
Socket activation mode is generally the default when running on a host
OS that uses systemd. To revert to the traditional mode, all the socket
unit files must be masked:
::
Traditional service mode
------------------------
$ systemctl mask virtnetworkd.socket virtnetworkd-ro.socket \
virtnetworkd-admin.socket
On hosts without systemd, it will create and listen on UNIX sockets itself.
OPTIONS

23
docs/manpages/virtnodedevd.rst
View File

@ -38,26 +38,25 @@ during startup. None the less it is recommended to avoid restarting with
running guests whenever practical.
SYSTEM SOCKET ACTIVATION
========================
DAEMON STARTUP MODES
====================
The ``virtnodedevd`` daemon is capable of starting in two modes.
In the traditional mode, it will create and listen on UNIX sockets itself.
In socket activation mode, it will rely on systemd to create and listen
on the UNIX sockets and pass them as pre-opened file descriptors. In this
mode most of the socket related config options in
Socket activation mode
----------------------
On hosts with systemd it is started in socket activation mode and it will rely
on systemd to create and listen on the UNIX sockets and pass them as pre-opened
file descriptors. In this mode most of the socket related config options in
``/etc/libvirt/virtnodedevd.conf`` will no longer have any effect.
Socket activation mode is generally the default when running on a host
OS that uses systemd. To revert to the traditional mode, all the socket
unit files must be masked:
::
Traditional service mode
------------------------
$ systemctl mask virtnodedevd.socket virtnodedevd-ro.socket \
virtnodedevd-admin.socket
On hosts without systemd, it will create and listen on UNIX sockets itself.
OPTIONS

23
docs/manpages/virtnwfilterd.rst
View File

@ -39,26 +39,25 @@ during startup. None the less it is recommended to avoid restarting with
running guests whenever practical.
SYSTEM SOCKET ACTIVATION
========================
DAEMON STARTUP MODES
====================
The ``virtnwfilterd`` daemon is capable of starting in two modes.
In the traditional mode, it will create and listen on UNIX sockets itself.
In socket activation mode, it will rely on systemd to create and listen
on the UNIX sockets and pass them as pre-opened file descriptors. In this
mode most of the socket related config options in
Socket activation mode
----------------------
On hosts with systemd it is started in socket activation mode and it will rely
on systemd to create and listen on the UNIX sockets and pass them as pre-opened
file descriptors. In this mode most of the socket related config options in
``/etc/libvirt/virtnwfilterd.conf`` will no longer have any effect.
Socket activation mode is generally the default when running on a host
OS that uses systemd. To revert to the traditional mode, all the socket
unit files must be masked:
::
Traditional service mode
------------------------
$ systemctl mask virtnwfilterd.socket virtnwfilterd-ro.socket \
virtnwfilterd-admin.socket
On hosts without systemd, it will create and listen on UNIX sockets itself.
OPTIONS

31
docs/manpages/virtproxyd.rst
View File

@ -48,20 +48,20 @@ and can be restarted at any time. Clients should expect to reconnect after
the restart.
SYSTEM SOCKET ACTIVATION
========================
DAEMON STARTUP MODES
====================
The ``virtproxyd`` daemon is capable of starting in two modes.
In the traditional mode, it will create and listen on UNIX sockets itself.
It will also listen on TCP/IP socket(s), according to the ``listen_tcp``
and ``listen_tls`` options in ``/etc/libvirt/virtproxyd.conf``
In socket activation mode, it will rely on systemd to create and listen
on the UNIX, and optionally TCP/IP, sockets and pass them as pre-opened
file descriptors. In this mode most of the socket related config options in
``/etc/libvirt/virtproxyd.conf`` will no longer have any effect. To enable
TCP or TLS sockets use either
Socket activation mode
----------------------
On hosts with systemd it is started in socket activation mode and it will rely
on systemd to create and listen on the UNIX, and optionally TCP/IP, sockets and
pass them as pre-opened file descriptors. In this mode most of the socket
related config options in ``/etc/libvirt/virtproxyd.conf`` will no longer have
any effect. To enable TCP or TLS sockets use either
::
@ -73,14 +73,13 @@ Or
$ systemctl start virtproxyd-tcp.socket
Socket activation mode is generally the default when running on a host
OS that uses systemd. To revert to the traditional mode, all the socket
unit files must be masked:
::
Traditional service mode
------------------------
$ systemctl mask virtproxyd.socket virtproxyd-ro.socket \
virtproxyd-admin.socket virtproxyd-tls.socket virtproxyd-tcp.socket
On hosts without systemd, it will create and listen on UNIX sockets itself.
It will also listen on TCP/IP socket(s), according to the ``listen_tcp``
and ``listen_tls`` options in ``/etc/libvirt/virtproxyd.conf``
OPTIONS

37
docs/manpages/virtqemud.rst
View File

@ -39,40 +39,25 @@ during startup. None the less it is recommended to avoid restarting with
running guests whenever practical.
SYSTEM SOCKET ACTIVATION
========================
DAEMON STARTUP MODES
====================
The ``virtqemud`` daemon is capable of starting in two modes.
In the traditional mode, it will create and listen on UNIX sockets itself.
In socket activation mode, it will rely on systemd to create and listen
on the UNIX sockets and pass them as pre-opened file descriptors. In this
mode most of the socket related config options in
Socket activation mode
----------------------
On hosts with systemd it is started in socket activation mode and it will rely
on systemd to create and listen on the UNIX sockets and pass them as pre-opened
file descriptors. In this mode most of the socket related config options in
``/etc/libvirt/virtqemud.conf`` will no longer have any effect.
Socket activation mode is generally the default when running on a host
OS that uses systemd. To revert to the traditional mode, all the socket
unit files must be masked:
::
Traditional service mode
------------------------
$ systemctl mask virtqemud.socket virtqemud-ro.socket \
virtqemud-admin.socket
If using libvirt-guests service then the ordering for that service needs to be
adapted so that it is ordered after the service unit instead of the socket unit.
Since dependencies and ordering cannot be changed with drop-in overrides, the
whole libvirt-guests unit file needs to be changed. In order to preserve such
change copy the installed ``/usr/lib/systemd/system/libvirt-guests.service`` to
``/etc/systemd/system/libvirt-guests.service`` and make the change there,
specifically make sure the ``After=`` ordering mentions ``virtqemud.service`` and
not ``virtqemud.socket``:
::
[Unit]
After=virtqemud.service
On hosts without systemd, it will create and listen on UNIX sockets itself.
OPTIONS

23
docs/manpages/virtsecretd.rst
View File

@ -38,26 +38,25 @@ during startup. None the less it is recommended to avoid restarting with
running guests whenever practical.
SYSTEM SOCKET ACTIVATION
========================
DAEMON STARTUP MODES
====================
The ``virtsecretd`` daemon is capable of starting in two modes.
In the traditional mode, it will create and listen on UNIX sockets itself.
In socket activation mode, it will rely on systemd to create and listen
on the UNIX sockets and pass them as pre-opened file descriptors. In this
mode most of the socket related config options in
Socket activation mode
----------------------
On hosts with systemd it is started in socket activation mode and it will rely
on systemd to create and listen on the UNIX sockets and pass them as pre-opened
file descriptors. In this mode most of the socket related config options in
``/etc/libvirt/virtsecretd.conf`` will no longer have any effect.
Socket activation mode is generally the default when running on a host
OS that uses systemd. To revert to the traditional mode, all the socket
unit files must be masked:
::
Traditional service mode
------------------------
$ systemctl mask virtsecretd.socket virtsecretd-ro.socket \
virtsecretd-admin.socket
On hosts without systemd, it will create and listen on UNIX sockets itself.
OPTIONS

23
docs/manpages/virtstoraged.rst
View File

@ -39,26 +39,25 @@ during startup. None the less it is recommended to avoid restarting with
running guests whenever practical.
SYSTEM SOCKET ACTIVATION
========================
DAEMON STARTUP MODES
====================
The ``virtstoraged`` daemon is capable of starting in two modes.
In the traditional mode, it will create and listen on UNIX sockets itself.
In socket activation mode, it will rely on systemd to create and listen
on the UNIX sockets and pass them as pre-opened file descriptors. In this
mode most of the socket related config options in
Socket activation mode
----------------------
On hosts with systemd it is started in socket activation mode and it will rely
on systemd to create and listen on the UNIX sockets and pass them as pre-opened
file descriptors. In this mode most of the socket related config options in
``/etc/libvirt/virtstoraged.conf`` will no longer have any effect.
Socket activation mode is generally the default when running on a host
OS that uses systemd. To revert to the traditional mode, all the socket
unit files must be masked:
::
Traditional service mode
------------------------
$ systemctl mask virtstoraged.socket virtstoraged-ro.socket \
virtstoraged-admin.socket
On hosts without systemd, it will create and listen on UNIX sockets itself.
OPTIONS

38
docs/manpages/virtvboxd.rst
View File

@ -37,40 +37,26 @@ Restarting ``virtvboxd`` does not interrupt running guests. Guests continue to
operate and changes in their state will generally be picked up automatically
during startup.
SYSTEM SOCKET ACTIVATION
========================
DAEMON STARTUP MODES
====================
The ``virtvboxd`` daemon is capable of starting in two modes.
In the traditional mode, it will create and listen on UNIX sockets itself.
In socket activation mode, it will rely on systemd to create and listen
on the UNIX sockets and pass them as pre-opened file descriptors. In this
mode most of the socket related config options in
Socket activation mode
----------------------
On hosts with systemd it is started in socket activation mode and it will rely
on systemd to create and listen on the UNIX sockets and pass them as pre-opened
file descriptors. In this mode most of the socket related config options in
``/etc/libvirt/virtvboxd.conf`` will no longer have any effect.
Socket activation mode is generally the default when running on a host
OS that uses systemd. To revert to the traditional mode, all the socket
unit files must be masked:
::
Traditional service mode
------------------------
$ systemctl mask virtvboxd.socket virtvboxd-ro.socket \
virtvboxd-admin.socket
If using libvirt-guests service then the ordering for that service needs to be
adapted so that it is ordered after the service unit instead of the socket unit.
Since dependencies and ordering cannot be changed with drop-in overrides, the
whole libvirt-guests unit file needs to be changed. In order to preserve such
change copy the installed ``/usr/lib/systemd/system/libvirt-guests.service`` to
``/etc/systemd/system/libvirt-guests.service`` and make the change there,
specifically make sure the ``After=`` ordering mentions ``virtvboxd.service`` and
not ``virtvboxd.socket``:
::
[Unit]
After=virtvboxd.service
On hosts without systemd, it will create and listen on UNIX sockets itself.
OPTIONS

37
docs/manpages/virtvzd.rst
View File

@ -39,40 +39,25 @@ during startup. None the less it is recommended to avoid restarting with
running guests whenever practical.
SYSTEM SOCKET ACTIVATION
========================
DAEMON STARTUP MODES
====================
The ``virtvzd`` daemon is capable of starting in two modes.
In the traditional mode, it will create and listen on UNIX sockets itself.
In socket activation mode, it will rely on systemd to create and listen
on the UNIX sockets and pass them as pre-opened file descriptors. In this
mode most of the socket related config options in
Socket activation mode
----------------------
On hosts with systemd it is started in socket activation mode and it will rely
on systemd to create and listen on the UNIX sockets and pass them as pre-opened
file descriptors. In this mode most of the socket related config options in
``/etc/libvirt/virtvzd.conf`` will no longer have any effect.
Socket activation mode is generally the default when running on a host
OS that uses systemd. To revert to the traditional mode, all the socket
unit files must be masked:
::
Traditional service mode
------------------------
$ systemctl mask virtvzd.socket virtvzd-ro.socket \
virtvzd-admin.socket
If using libvirt-guests service then the ordering for that service needs to be
adapted so that it is ordered after the service unit instead of the socket unit.
Since dependencies and ordering cannot be changed with drop-in overrides, the
whole libvirt-guests unit file needs to be changed. In order to preserve such
change copy the installed ``/usr/lib/systemd/system/libvirt-guests.service`` to
``/etc/systemd/system/libvirt-guests.service`` and make the change there,
specifically make sure the ``After=`` ordering mentions ``virtvzd.service`` and
not ``virtvzd.socket``:
::
[Unit]
After=virtvzd.service
On hosts without systemd, it will create and listen on UNIX sockets itself.
OPTIONS

37
docs/manpages/virtxend.rst
View File

@ -39,40 +39,25 @@ during startup. None the less it is recommended to avoid restarting with
running guests whenever practical.
SYSTEM SOCKET ACTIVATION
========================
DAEMON STARTUP MODES
====================
The ``virtxend`` daemon is capable of starting in two modes.
In the traditional mode, it will create and listen on UNIX sockets itself.
In socket activation mode, it will rely on systemd to create and listen
on the UNIX sockets and pass them as pre-opened file descriptors. In this
mode most of the socket related config options in
Socket activation mode
----------------------
On hosts with systemd it is started in socket activation mode and it will rely
on systemd to create and listen on the UNIX sockets and pass them as pre-opened
file descriptors. In this mode most of the socket related config options in
``/etc/libvirt/virtxend.conf`` will no longer have any effect.
Socket activation mode is generally the default when running on a host
OS that uses systemd. To revert to the traditional mode, all the socket
unit files must be masked:
::
Traditional service mode
------------------------
$ systemctl mask virtxend.socket virtxend-ro.socket \
virtxend-admin.socket
If using libvirt-guests service then the ordering for that service needs to be
adapted so that it is ordered after the service unit instead of the socket unit.
Since dependencies and ordering cannot be changed with drop-in overrides, the
whole libvirt-guests unit file needs to be changed. In order to preserve such
change copy the installed ``/usr/lib/systemd/system/libvirt-guests.service`` to
``/etc/systemd/system/libvirt-guests.service`` and make the change there,
specifically make sure the ``After=`` ordering mentions ``virtxend.service`` and
not ``virtxend.socket``:
::
[Unit]
After=virtxend.service
On hosts without systemd, it will create and listen on UNIX sockets itself.
OPTIONS