f53988d657
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 59d30adacd 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>
5.8 KiB
virtqemud
libvirt QEMU management daemon
- Manual section
8
- Manual group
Virtualization Support
SYNOPSIS
virtqemud [OPTION]...
DESCRIPTION
The virtqemud program is a server side daemon component of the libvirt virtualization management system.
It is one of a collection of modular daemons that replace functionality previously provided by the monolithic libvirtd daemon.
This daemon runs on virtualization hosts to provide management for QEMU virtual machines.
The virtqemud daemon only listens for requests on a local Unix domain socket. Remote off-host access and backwards compatibility with legacy clients expecting libvirtd is provided by the virtproxy daemon.
Restarting virtqemud does not interrupt running guests. Guests continue to operate and changes in their state will generally be picked up automatically during startup. None the less it is recommended to avoid restarting with running guests whenever practical.
DAEMON STARTUP MODES
The virtqemud daemon is capable of starting in two modes.
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.
Traditional service mode
On hosts without systemd, it will create and listen on UNIX sockets itself.
OPTIONS
-h, --help
Display command line help usage then exit.
-d, --daemon
Run as a daemon & write PID file.
-f, --config *FILE*
Use this configuration file, overriding the default value.
-p, --pid-file *FILE*
Use this name for the PID file, overriding the default value.
-t, --timeout *SECONDS*
Exit after timeout period (in seconds), provided there are neither any client connections nor any running domains.
-v, --verbose
Enable output of verbose messages.
--version
Display version information then exit.
SIGNALS
On receipt of SIGHUP virtqemud will reload its configuration.
FILES
When run as root
@SYSCONFDIR@/libvirt/virtqemud.conf
The default configuration file used by virtqemud, unless overridden on the command line using the -f | --config option.
In addition to the default configuration file, virtqemud reads configuration for the QEMU driver from:
@SYSCONFDIR@/libvirt/qemu.conf
This file contains various knobs and default values for virtual machines created within QEMU driver, and offers a way to override the built in defaults, for instance (but not limited to): paths to various supplementary binaries, TLS certificates location, graphical consoles configuration and others. Location of this file can't be overridden by any command line switch.
@RUNSTATEDIR@/libvirt/virtqemud-sock@RUNSTATEDIR@/libvirt/virtqemud-sock-ro@RUNSTATEDIR@/libvirt/virtqemud-admin-sock
The sockets virtqemud will use.
The TLS Server private key virtqemud will use.
@RUNSTATEDIR@/virtqemud.pid
The PID file to use, unless overridden by the -p | --pid-file option.
When run as non-root
$XDG_CONFIG_HOME/libvirt/virtqemud.conf
The default configuration file used by virtqemud, unless overridden on the command line using the -f|--config option.
In addition to the default configuration file, virtqemud reads configuration for the qemu driver from:
$XDG_CONFIG_HOME/libvirt/qemu.conf
If the file exists, it can contain various knobs and default values for virtual machines created within QEMU driver, and offers a way to override the built in defaults, for instance (but not limited to): paths to various supplementary binaries, TLS certificates location, graphical consoles configuration and others. Location of this file can't be overridden by any command line switch.
$XDG_RUNTIME_DIR/libvirt/virtqemud-sock$XDG_RUNTIME_DIR/libvirt/virtqemud-admin-sock
The sockets virtqemud will use.
$XDG_RUNTIME_DIR/libvirt/virtqemud.pid
The PID file to use, unless overridden by the -p|--pid-file option.
If $XDG_CONFIG_HOME is not set in your environment, virtqemud will use $HOME/.config
If $XDG_RUNTIME_DIR is not set in your environment, virtqemud will use $HOME/.cache
EXAMPLES
To retrieve the version of virtqemud:
# virtqemud --version
virtqemud (libvirt) @VERSION@To start virtqemud, instructing it to daemonize and create a PID file:
# virtqemud -d
# ls -la @RUNSTATEDIR@/virtqemud.pid
-rw-r--r-- 1 root root 6 Jul 9 02:40 @RUNSTATEDIR@/virtqemud.pidBUGS
Please report all bugs you discover. This should be done via either:
the mailing list
the bug tracker
Alternatively, you may report bugs to your software distributor / vendor.
AUTHORS
Please refer to the AUTHORS file distributed with libvirt.
COPYRIGHT
Copyright (C) 2006-2020 Red Hat, Inc., and the authors listed in the libvirt AUTHORS file.
LICENSE
virtqemud is distributed under the terms of the GNU LGPL v2.1+. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE
SEE ALSO
virsh(1), libvirtd(8), https://www.libvirt.org/daemons.html, https://www.libvirt.org/drvqemu.html