libvirtd

package: libvirt-daemon

title: libvirtd(8)

summary: libvirt management daemon

text:
# libvirtd(8)

## NAME
libvirtd - libvirt management daemon

## SYNOPSIS
libvirtd [OPTION]...

## DESCRIPTION
The libvirtd program is the server side daemon component of the libvirt virtualization management system.

This daemon runs on host servers and performs required management tasks for virtualized guests. This includes activities such as starting, stopping and migrating guests between host servers, configuring and manipulating networking, and managing storage for use by guests.

The libvirt client libraries and utilities connect to this daemon to issue tasks and collect information about the configuration and resources of the host system and guests.

By default, the libvirtd daemon listens for requests on a local Unix domain socket. Using the -l | --listen command line option, the libvirtd daemon can be instructed to additionally listen on a TCP/IP socket. The TCP/IP socket to use is defined in the libvirtd configuration file.

Restarting libvirtd does not impact running guests. Guests continue to operate and will be picked up automatically if their XML configuration has been defined. Any guests whose XML configuration has not been defined will be lost from the configuration.

## SYSTEM SOCKET ACTIVATION
The libvirtd daemon is capable of starting in two modes.

In the traditional mode, it will create and listen on UNIX sockets itself. If the --listen parameter is given, it will also listen on TCP/IP socket(s), according to the listen_tcp and listen_tls options in /etc/libvirt/libvirtd.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, it is not permitted to pass the --listen parameter, and most of the socket related config options in /etc/libvirt/libvirtd.conf will no longer have any effect. To enable TCP or TLS sockets use either

```
$ systemctl start libvirtd-tls.socket
```

Or

```
$ systemctl start libvirtd-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:

```
$ systemctl mask libvirtd.socket libvirtd-ro.socket \

   libvirtd-admin.socket libvirtd-tls.socket libvirtd-tcp.socket
```

On top of that make sure that the --timeout argument is not used for the daemon since it would not be started upon any later connection.

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 libvirtd.service and not libvirtd.socket:

```
[Unit]
After=libvirtd.service
```

## 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.

-l, --listen

Listen for TCP/IP connections. This should not be set if using systemd socket activation. Instead activate the libvirtd-tls.socket or libvirtd-tcp.socket unit files.

-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 libvirtd will reload its configuration.

## FILES

### When run as root
•

/etc/libvirt/libvirtd.conf

The default configuration file used by libvirtd, unless overridden on the command line using the -f | --config option.

Depending on what driver is installed, then the following files are also read:

- /etc/libvirt/qemu.conf for the QEMU driver

- /etc/libvirt/lxc.conf for the LXC driver

- /etc/libvirt/libxl.conf for the libxl driver

These files contain various knobs and default values for virtual machines created within their respective drivers, and offer 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 neither of these files can be overridden by any command line switch.

- /run/libvirt/libvirt-sock

- /run/libvirt/libvirt-sock-ro

The sockets libvirtd will use.

•

/etc/pki/CA/cacert.pem

The TLS Certificate Authority certificate libvirtd will use.

•

/etc/pki/libvirt/servercert.pem

The TLS Server certificate libvirtd will use.

•

/etc/pki/libvirt/private/serverkey.pem

The TLS Server private key libvirtd will use.

•

/run/libvirtd.pid

The PID file to use, unless overridden by the -p | --pid-file option.

### When run as non-root
•

$XDG_CONFIG_HOME/libvirt/libvirtd.conf

The default configuration file used by libvirtd, unless overridden on the command line using the -f``|--config`` option.

If QEMU driver is installed, then the following file is also read:

•

$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/libvirt-sock

The socket libvirtd will use.

•

$HOME/.pki/libvirt/cacert.pem

The TLS Certificate Authority certificate libvirtd will use.

•

$HOME/.pki/libvirt/servercert.pem

The TLS Server certificate libvirtd will use.

•

$HOME/.pki/libvirt/serverkey.pem

The TLS Server private key libvirtd will use.

•

$XDG_RUNTIME_DIR/libvirt/libvirtd.pid

The PID file to use, unless overridden by the -p``|--pid-file`` option.

If $XDG_CONFIG_HOME is not set in your environment, libvirtd will use $HOME/.config

If $XDG_RUNTIME_DIR is not set in your environment, libvirtd will use $HOME/.cache

## EXAMPLES
To retrieve the version of libvirtd:

```
# libvirtd --version
libvirtd (libvirt) 11.10.0
```

To start libvirtd, instructing it to daemonize and create a PID file:

```
# libvirtd -d
# ls -la /run/libvirtd.pid
-rw-r--r-- 1 root root 6 Jul  9 02:40 /run/libvirtd.pid
```

## BUGS
Please report all bugs you discover. This should be done via either:

1.

the mailing list https://libvirt.org/contact.html

2.

the bug tracker https://libvirt.org/bugs.html

Alternatively, you may report bugs to your software distributor / vendor.

## AUTHORS
Please refer to the AUTHORS file distributed with libvirt.

## COPYRIGHT
Copyright (C) 2006-2012 Red Hat, Inc., and the authors listed in the libvirt AUTHORS file.

## LICENSE
libvirtd 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), virt-install(1), virt-xml-validate(1), virt-top(1), virt-df(1), https://libvirt.org/


libvirt-guests

package: libvirt-daemon-common

title: libvirt-guests(8)

summary: suspend/resume running libvirt guests

text:
# libvirt-guests(8)

## NAME
libvirt-guests - suspend/resume running libvirt guests

## SYNOPSIS
libvirt-guests COMMAND

## DESCRIPTION
libvirt-guests is a service that can be used to coordinate guest and host lifecycle actions. By default, libvirt-guests will suspend running guests when the host shuts down, and restore them to their pre-shutdown state when the host reboots.

libvirt-guests is typically under control of systemd. When libvirt-guests.service is enabled, systemd will call libvirt-guests with the start COMMAND when the host boots. Conversely, systemd will call libvirt-guests with the stop COMMAND when the host shuts down.

libvirt-guests can be used directly. In addition to the start and stop COMMANDs, it also supports status, restart, condrestart, try-restart, reload, force-reload, gueststatus, and shutdown COMMANDs.

## FILES
libvirt-guests defines several variables to control service behavior. The default value of these variables can be overridden in:

•

/etc/sysconfig/libvirt-guests

The following variables are supported:

- URIS=default URIs to check for running guests. Example: URIS='default xen:///system xen+tcp://host/system lxc:///system'

- ON_BOOT=start Action taken on host boot

- start All guests which were running on shutdown are started on boot regardless of their autostart settings

- ignore libvirt-guests won't start any guest on boot, however, guests marked as autostart will still be automatically started by libvirtd

- START_DELAY=0 Number of seconds to wait between each guest start. Set to 0 to allow parallel startup.

- ON_SHUTDOWN=suspend Action taken on host shutdown

- suspend All running guests are suspended using virsh managedsave

- shutdown All running guests are asked to shutdown. Please be careful with this settings since there is no way to distinguish between a guest which is stuck or ignores shutdown requests and a guest which just needs a long time to shutdown. When setting ON_SHUTDOWN=shutdown, you must also set SHUTDOWN_TIMEOUT to a value suitable for your guests.

- PARALLEL_SHUTDOWN=0 Number of guests will be shutdown concurrently, taking effect when "ON_SHUTDOWN" is set to "shutdown". If Set to 0, guests will be shutdown one after another. Number of guests on shutdown at any time will not exceed number set in this variable.

- SHUTDOWN_TIMEOUT=300 Number of seconds we're willing to wait for a guest to shut down. If parallel shutdown is enabled, this timeout applies as a timeout for shutting down all guests on a single URI defined in the variable URIS. If this is 0, then there is no time out (use with caution, as guests might not respond to a shutdown request). The default value is 300 seconds (5 minutes).

- BYPASS_CACHE=0 If non-zero, try to bypass the file system cache when saving and restoring guests, even though this may give slower operation for some file systems.

- SYNC_TIME=0 If non-zero, try to sync guest time on domain resume. Be aware, that this requires guest agent with support for time synchronization running in the guest. By default, this functionality is turned off.

- PERSISTENT_ONLY=default Defines what type of guest virtual machine ON_SHUTDOWN action is applied to

- default This implements the already existing default behavior. If ON_SHUTDOWN action is shutdown, transient and persistent guest virtual machines are asked to shutdown. If ON_SHUTDOWN action is suspend, only persistent guest virtual machines are asked to suspend.

- true ON_SHUTDOWN action is executed only on persistent guest virtual machines. Transient guest virtual machines are not affected.

- false ON_SHUTDOWN action is executed on persistent and transient guest virtual machines.

## BUGS
Please report all bugs you discover. This should be done via either:

1.

the mailing list https://libvirt.org/contact.html

2.

the bug tracker https://libvirt.org/bugs.html

Alternatively, you may report bugs to your software distributor / vendor.

## AUTHORS
Please refer to the AUTHORS file distributed with libvirt.

## LICENSE
libvirt-guests 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
libvirtd(8), https://libvirt.org/


virt-ssh-helper

title: virt-ssh-helper(8)

summary: libvirt socket proxy

text:
# virt-ssh-helper(8)

## NAME
virt-ssh-helper - libvirt socket proxy

## SYNOPSIS
virt-ssh-helper [OPTION]... URI

## DESCRIPTION
virt-ssh-helper is an internal tool used to handle connections coming from remote clients, and it's not intended to be called directly by the user.

## OPTIONS
URI

Local libvirt URI to connect the remote client to.

-r, --readonly

Make the connection read-only.

-h, --help

Display command line help usage then exit.

-V, --version

Display version information then exit.

## EXIT STATUS
The exit status will be zero on success, non-zero on failure.

## AUTHOR
Daniel P. Berrangé

## BUGS
Please report all bugs you discover. This should be done via either:

1.

the mailing list https://libvirt.org/contact.html

2.

the bug tracker https://libvirt.org/bugs.html

Alternatively, you may report bugs to your software distributor / vendor.

## COPYRIGHT
Copyright (C) 2020 Red Hat, Inc.

## LICENSE
virt-ssh-helper is distributed under the terms of the GNU LGPL v2+. 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), https://libvirt.org/


virtinterfaced

package: libvirt-daemon-driver-interface

title: virtinterfaced(8)

text:
# virtinterfaced(8)

## NAME
virtinterfaced - libvirt host network interface management daemon

## SYNOPSIS
virtinterfaced [OPTION]...

## DESCRIPTION
The virtinterfaced 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 host network interfaces.

The virtinterfaced daemon only listens for requests on a local Unix domain socket. Remote access via TLS/TCP and backwards compatibility with legacy clients expecting libvirtd is provided by the virtproxyd daemon.

Restarting virtinterfaced 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 virtinterfaced 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/virtinterfaced.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 no client connections.

-v, --verbose

Enable output of verbose messages.

--version

Display version information then exit.

## SIGNALS
On receipt of SIGHUP virtinterfaced will reload its configuration.

## FILES

### When run as root
•

/etc/libvirt/virtinterfaced.conf

The default configuration file used by virtinterfaced, unless overridden on the command line using the -f | --config option.

- /run/libvirt/virtinterfaced-sock

- /run/libvirt/virtinterfaced-sock-ro

- /run/libvirt/virtinterfaced-admin-sock

The sockets virtinterfaced will use.

The TLS Server private key virtinterfaced will use.

•

/run/virtinterfaced.pid

The PID file to use, unless overridden by the -p | --pid-file option.

### When run as non-root
•

$XDG_CONFIG_HOME/libvirt/virtinterfaced.conf

The default configuration file used by virtinterfaced, unless overridden on the command line using the -f``|--config`` option.

- $XDG_RUNTIME_DIR/libvirt/virtinterfaced-sock

- $XDG_RUNTIME_DIR/libvirt/virtinterfaced-admin-sock

The sockets virtinterfaced will use.

•

$XDG_RUNTIME_DIR/libvirt/virtinterfaced.pid

The PID file to use, unless overridden by the -p``|--pid-file`` option.

If $XDG_CONFIG_HOME is not set in your environment, virtinterfaced will use $HOME/.config

If $XDG_RUNTIME_DIR is not set in your environment, virtinterfaced will use $HOME/.cache

## EXAMPLES
To retrieve the version of virtinterfaced:

```
# virtinterfaced --version
virtinterfaced (libvirt) 11.10.0
```

To start virtinterfaced, instructing it to daemonize and create a PID file:

```
# virtinterfaced -d
# ls -la /run/virtinterfaced.pid
-rw-r--r-- 1 root root 6 Jul  9 02:40 /run/virtinterfaced.pid
```

## BUGS
Please report all bugs you discover. This should be done via either:

1.

the mailing list https://libvirt.org/contact.html

2.

the bug tracker https://libvirt.org/bugs.html

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
virtinterfaced 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://libvirt.org/daemons.html,


virtlxcd

package: libvirt-daemon-driver-lxc

title: virtlxcd(8)

summary: libvirt LXC management daemon

text:
# virtlxcd(8)

## NAME
virtlxcd - libvirt LXC management daemon

## SYNOPSIS
virtlxcd [OPTION]...

## DESCRIPTION
The virtlxcd 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 LXC containers.

The virtlxcd daemon only listens for requests on a local Unix domain socket. Remote access via TLS/TCP and backwards compatibility with legacy clients expecting libvirtd is provided by the virtproxyd daemon.

Restarting virtlxcd 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 virtlxcd 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/virtlxcd.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 virtlxcd will reload its configuration.

## FILES
The virtlxcd program must be ran as root. Trying to start the program under a different user results in error.

•

/etc/libvirt/virtlxcd.conf

The default configuration file used by virtlxcd, unless overridden on the command line using the -f | --config option.

In addition to the default configuration file, virtlxcd reads configuration for the LXC driver from:

•

/etc/libvirt/lxc.conf

This file contains various knobs and default values for virtual machines created within LXC driver, and offers a way to override the built in defaults, Location of this file can't be overridden by any command line switch.

- /run/libvirt/virtlxcd-sock

- /run/libvirt/virtlxcd-sock-ro

- /run/libvirt/virtlxcd-admin-sock

The sockets virtlxcd will use.

The TLS Server private key virtlxcd will use.

•

/run/virtlxcd.pid

The PID file to use, unless overridden by the -p | --pid-file option.

## EXAMPLES
To retrieve the version of virtlxcd:

```
# virtlxcd --version
virtlxcd (libvirt) 11.10.0
```

To start virtlxcd, instructing it to daemonize and create a PID file:

```
# virtlxcd -d
# ls -la /run/virtlxcd.pid
-rw-r--r-- 1 root root 6 Jul  9 02:40 /run/virtlxcd.pid
```

## BUGS
Please report all bugs you discover. This should be done via either:

1.

the mailing list https://libvirt.org/contact.html

2.

the bug tracker https://libvirt.org/bugs.html

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
virtlxcd 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://libvirt.org/daemons.html, https://libvirt.org/drvlxc.html


virtnetworkd

package: libvirt-daemon-driver-network

title: virtnetworkd(8)

text:
# virtnetworkd(8)

## NAME
virtnetworkd - libvirt virtual network management daemon

## SYNOPSIS
virtnetworkd [OPTION]...

## DESCRIPTION
The virtnetworkd 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 virtual networks.

The virtnetworkd daemon only listens for requests on a local Unix domain socket. Remote access via TLS/TCP and backwards compatibility with legacy clients expecting libvirtd is provided by the virtproxyd daemon.

Restarting virtnetworkd 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 virtnetworkd 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/virtnetworkd.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 no client connections.

-v, --verbose

Enable output of verbose messages.

--version

Display version information then exit.

## SIGNALS
On receipt of SIGHUP virtnetworkd will reload its configuration.

## FILES

### When run as root
•

/etc/libvirt/virtnetworkd.conf

The default configuration file used by virtnetworkd, unless overridden on the command line using the -f | --config option.

- /run/libvirt/virtnetworkd-sock

- /run/libvirt/virtnetworkd-sock-ro

- /run/libvirt/virtnetworkd-admin-sock

The sockets virtnetworkd will use.

The TLS Server private key virtnetworkd will use.

•

/run/virtnetworkd.pid

The PID file to use, unless overridden by the -p | --pid-file option.

### When run as non-root
•

$XDG_CONFIG_HOME/libvirt/virtnetworkd.conf

The default configuration file used by virtnetworkd, unless overridden on the command line using the -f``|--config`` option.

- $XDG_RUNTIME_DIR/libvirt/virtnetworkd-sock

- $XDG_RUNTIME_DIR/libvirt/virtnetworkd-admin-sock

The sockets virtnetworkd will use.

•

$XDG_RUNTIME_DIR/libvirt/virtnetworkd.pid

The PID file to use, unless overridden by the -p``|--pid-file`` option.

If $XDG_CONFIG_HOME is not set in your environment, virtnetworkd will use $HOME/.config

If $XDG_RUNTIME_DIR is not set in your environment, virtnetworkd will use $HOME/.cache

## EXAMPLES
To retrieve the version of virtnetworkd:

```
# virtnetworkd --version
virtnetworkd (libvirt) 11.10.0
```

To start virtnetworkd, instructing it to daemonize and create a PID file:

```
# virtnetworkd -d
# ls -la /run/virtnetworkd.pid
-rw-r--r-- 1 root root 6 Jul  9 02:40 /run/virtnetworkd.pid
```

## BUGS
Please report all bugs you discover. This should be done via either:

1.

the mailing list https://libvirt.org/contact.html

2.

the bug tracker https://libvirt.org/bugs.html

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
virtnetworkd 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://libvirt.org/daemons.html,


virtnodedevd

package: libvirt-daemon-driver-nodedev

title: virtnodedevd(8)

summary: libvirt host device management daemon

text:
# virtnodedevd(8)

## NAME
virtnodedevd - libvirt host device management daemon

## SYNOPSIS
virtnodedevd [OPTION]...

## DESCRIPTION
The virtnodedevd 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 host devices.

The virtnodedevd daemon only listens for requests on a local Unix domain socket. Remote access via TLS/TCP and backwards compatibility with legacy clients expecting libvirtd is provided by the virtproxyd daemon.

Restarting virtnodedevd 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 virtnodedevd 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/virtnodedevd.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 no client connections.

-v, --verbose

Enable output of verbose messages.

--version

Display version information then exit.

## SIGNALS
On receipt of SIGHUP virtnodedevd will reload its configuration.

## FILES

### When run as root
•

/etc/libvirt/virtnodedevd.conf

The default configuration file used by virtnodedevd, unless overridden on the command line using the -f | --config option.

- /run/libvirt/virtnodedevd-sock

- /run/libvirt/virtnodedevd-sock-ro

- /run/libvirt/virtnodedevd-admin-sock

The sockets virtnodedevd will use.

The TLS Server private key virtnodedevd will use.

•

/run/virtnodedevd.pid

The PID file to use, unless overridden by the -p | --pid-file option.

### When run as non-root
•

$XDG_CONFIG_HOME/libvirt/virtnodedevd.conf

The default configuration file used by virtnodedevd, unless overridden on the command line using the -f``|--config`` option.

- $XDG_RUNTIME_DIR/libvirt/virtnodedevd-sock

- $XDG_RUNTIME_DIR/libvirt/virtnodedevd-admin-sock

The sockets virtnodedevd will use.

•

$XDG_RUNTIME_DIR/libvirt/virtnodedevd.pid

The PID file to use, unless overridden by the -p``|--pid-file`` option.

If $XDG_CONFIG_HOME is not set in your environment, virtnodedevd will use $HOME/.config

If $XDG_RUNTIME_DIR is not set in your environment, virtnodedevd will use $HOME/.cache

## EXAMPLES
To retrieve the version of virtnodedevd:

```
# virtnodedevd --version
virtnodedevd (libvirt) 11.10.0
```

To start virtnodedevd, instructing it to daemonize and create a PID file:

```
# virtnodedevd -d
# ls -la /run/virtnodedevd.pid
-rw-r--r-- 1 root root 6 Jul  9 02:40 /run/virtnodedevd.pid
```

## BUGS
Please report all bugs you discover. This should be done via either:

1.

the mailing list https://libvirt.org/contact.html

2.

the bug tracker https://libvirt.org/bugs.html

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
virtnodedevd 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://libvirt.org/daemons.html, https://libvirt.org/drvnodedev.html


virtnwfilterd

package: libvirt-daemon-driver-nwfilter

title: virtnwfilterd(8)

text:
# virtnwfilterd(8)

## NAME
virtnwfilterd - libvirt network filter management daemon

## SYNOPSIS
virtnwfilterd [OPTION]...

## DESCRIPTION
The virtnwfilterd 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 network filters.

The virtnwfilterd daemon only listens for requests on a local Unix domain socket. Remote access via TLS/TCP and backwards compatibility with legacy clients expecting libvirtd is provided by the virtproxyd daemon.

Restarting virtnwfilterd 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 virtnwfilterd 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/virtnwfilterd.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 no client connections.

-v, --verbose

Enable output of verbose messages.

--version

Display version information then exit.

## SIGNALS
On receipt of SIGHUP virtnwfilterd will reload its configuration.

## FILES

### When run as root
•

/etc/libvirt/virtnwfilterd.conf

The default configuration file used by virtnwfilterd, unless overridden on the command line using the -f | --config option.

- /run/libvirt/virtnwfilterd-sock

- /run/libvirt/virtnwfilterd-sock-ro

- /run/libvirt/virtnwfilterd-admin-sock

The sockets virtnwfilterd will use.

The TLS Server private key virtnwfilterd will use.

•

/run/virtnwfilterd.pid

The PID file to use, unless overridden by the -p | --pid-file option.

### When run as non-root
•

$XDG_CONFIG_HOME/libvirt/virtnwfilterd.conf

The default configuration file used by virtnwfilterd, unless overridden on the command line using the -f``|--config`` option.

- $XDG_RUNTIME_DIR/libvirt/virtnwfilterd-sock

- $XDG_RUNTIME_DIR/libvirt/virtnwfilterd-admin-sock

The sockets virtnwfilterd will use.

•

$XDG_RUNTIME_DIR/libvirt/virtnwfilterd.pid

The PID file to use, unless overridden by the -p``|--pid-file`` option.

If $XDG_CONFIG_HOME is not set in your environment, virtnwfilterd will use $HOME/.config

If $XDG_RUNTIME_DIR is not set in your environment, virtnwfilterd will use $HOME/.cache

## EXAMPLES
To retrieve the version of virtnwfilterd:

```
# virtnwfilterd --version
virtnwfilterd (libvirt) 11.10.0
```

To start virtnwfilterd, instructing it to daemonize and create a PID file:

```
# virtnwfilterd -d
# ls -la /run/virtnwfilterd.pid
-rw-r--r-- 1 root root 6 Jul  9 02:40 /run/virtnwfilterd.pid
```

## BUGS
Please report all bugs you discover. This should be done via either:

1.

the mailing list https://libvirt.org/contact.html

2.

the bug tracker https://libvirt.org/bugs.html

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
virtnwfilterd 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://libvirt.org/daemons.html,


virtqemud

package: libvirt-daemon-driver-qemu

title: virtqemud(8)

summary: libvirt QEMU management daemon

text:
# virtqemud(8)

## NAME
virtqemud - libvirt QEMU management daemon

## 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 access via TLS/TCP and backwards compatibility with legacy clients expecting libvirtd is provided by the virtproxyd 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
•

/etc/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:

•

/etc/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.

- /run/libvirt/virtqemud-sock

- /run/libvirt/virtqemud-sock-ro

- /run/libvirt/virtqemud-admin-sock

The sockets virtqemud will use.

The TLS Server private key virtqemud will use.

•

/run/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) 11.10.0
```

To start virtqemud, instructing it to daemonize and create a PID file:

```
# virtqemud -d
# ls -la /run/virtqemud.pid
-rw-r--r-- 1 root root 6 Jul  9 02:40 /run/virtqemud.pid
```

## BUGS
Please report all bugs you discover. This should be done via either:

1.

the mailing list https://libvirt.org/contact.html

2.

the bug tracker https://libvirt.org/bugs.html

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://libvirt.org/daemons.html, https://libvirt.org/drvqemu.html


virtsecretd

package: libvirt-daemon-driver-secret

title: virtsecretd(8)

summary: libvirt secret data management daemon

text:
# virtsecretd(8)

## NAME
virtsecretd - libvirt secret data management daemon

## SYNOPSIS
virtsecretd [OPTION]...

## DESCRIPTION
The virtsecretd 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 secret data.

The virtsecretd daemon only listens for requests on a local Unix domain socket. Remote access via TLS/TCP and backwards compatibility with legacy clients expecting libvirtd is provided by the virtproxyd daemon.

Restarting virtsecretd 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 virtsecretd 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/virtsecretd.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 ephemeral secrets.

-v, --verbose

Enable output of verbose messages.

--version

Display version information then exit.

## SIGNALS
On receipt of SIGHUP virtsecretd will reload its configuration.

## FILES

### When run as root
•

/etc/libvirt/virtsecretd.conf

The default configuration file used by virtsecretd, unless overridden on the command line using the -f | --config option.

- /run/libvirt/virtsecretd-sock

- /run/libvirt/virtsecretd-sock-ro

- /run/libvirt/virtsecretd-admin-sock

The sockets virtsecretd will use.

The TLS Server private key virtsecretd will use.

•

/run/virtsecretd.pid

The PID file to use, unless overridden by the -p | --pid-file option.

### When run as non-root
•

$XDG_CONFIG_HOME/libvirt/virtsecretd.conf

The default configuration file used by virtsecretd, unless overridden on the command line using the -f``|--config`` option.

- $XDG_RUNTIME_DIR/libvirt/virtsecretd-sock

- $XDG_RUNTIME_DIR/libvirt/virtsecretd-admin-sock

The sockets virtsecretd will use.

•

$XDG_RUNTIME_DIR/libvirt/virtsecretd.pid

The PID file to use, unless overridden by the -p``|--pid-file`` option.

If $XDG_CONFIG_HOME is not set in your environment, virtsecretd will use $HOME/.config

If $XDG_RUNTIME_DIR is not set in your environment, virtsecretd will use $HOME/.cache

## EXAMPLES
To retrieve the version of virtsecretd:

```
# virtsecretd --version
virtsecretd (libvirt) 11.10.0
```

To start virtsecretd, instructing it to daemonize and create a PID file:

```
# virtsecretd -d
# ls -la /run/virtsecretd.pid
-rw-r--r-- 1 root root 6 Jul  9 02:40 /run/virtsecretd.pid
```

## BUGS
Please report all bugs you discover. This should be done via either:

1.

the mailing list https://libvirt.org/contact.html

2.

the bug tracker https://libvirt.org/bugs.html

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
virtsecretd 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://libvirt.org/daemons.html, https://libvirt.org/drvsecret.html


virtstoraged

package: libvirt-daemon-driver-storage-core

title: virtstoraged(8)

summary: libvirt storage pool management daemon

text:
# virtstoraged(8)

## NAME
virtstoraged - libvirt storage pool management daemon

## SYNOPSIS
virtstoraged [OPTION]...

## DESCRIPTION
The virtstoraged 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 storage pools.

The virtstoraged daemon only listens for requests on a local Unix domain socket. Remote access via TLS/TCP and backwards compatibility with legacy clients expecting libvirtd is provided by the virtproxyd daemon.

Restarting virtstoraged 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 virtstoraged 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/virtstoraged.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 no client connections.

-v, --verbose

Enable output of verbose messages.

--version

Display version information then exit.

## SIGNALS
On receipt of SIGHUP virtstoraged will reload its configuration.

## FILES

### When run as root
•

/etc/libvirt/virtstoraged.conf

The default configuration file used by virtstoraged, unless overridden on the command line using the -f | --config option.

- /run/libvirt/virtstoraged-sock

- /run/libvirt/virtstoraged-sock-ro

- /run/libvirt/virtstoraged-admin-sock

The sockets virtstoraged will use.

The TLS Server private key virtstoraged will use.

•

/run/virtstoraged.pid

The PID file to use, unless overridden by the -p | --pid-file option.

### When run as non-root
•

$XDG_CONFIG_HOME/libvirt/virtstoraged.conf

The default configuration file used by virtstoraged, unless overridden on the command line using the -f``|--config`` option.

- $XDG_RUNTIME_DIR/libvirt/virtstoraged-sock

- $XDG_RUNTIME_DIR/libvirt/virtstoraged-admin-sock

The sockets virtstoraged will use.

•

$XDG_RUNTIME_DIR/libvirt/virtstoraged.pid

The PID file to use, unless overridden by the -p``|--pid-file`` option.

If $XDG_CONFIG_HOME is not set in your environment, virtstoraged will use $HOME/.config

If $XDG_RUNTIME_DIR is not set in your environment, virtstoraged will use $HOME/.cache

## EXAMPLES
To retrieve the version of virtstoraged:

```
# virtstoraged --version
virtstoraged (libvirt) 11.10.0
```

To start virtstoraged, instructing it to daemonize and create a PID file:

```
# virtstoraged -d
# ls -la /run/virtstoraged.pid
-rw-r--r-- 1 root root 6 Jul  9 02:40 /run/virtstoraged.pid
```

## BUGS
Please report all bugs you discover. This should be done via either:

1.

the mailing list https://libvirt.org/contact.html

2.

the bug tracker https://libvirt.org/bugs.html

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
virtstoraged 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://libvirt.org/daemons.html, https://libvirt.org/storage.html


virtvboxd

package: libvirt-daemon-driver-vbox

title: virtvboxd(8)

summary: libvirt VirtualBox management daemon

text:
# virtvboxd(8)

## NAME
virtvboxd - libvirt VirtualBox management daemon

## SYNOPSIS
virtvboxd [OPTION]...

## DESCRIPTION
The virtvboxd 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 VirtualBox virtual machines.

The virtvboxd daemon only listens for requests on a local Unix domain socket. Remote access via TLS/TCP and backwards compatibility with legacy clients expecting libvirtd is provided by the virtproxyd daemon.

Restarting virtvboxd does not interrupt running guests. Guests continue to operate and changes in their state will generally be picked up automatically during startup.

## DAEMON STARTUP MODES
The virtvboxd 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/virtvboxd.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 no client connections.

-v, --verbose

Enable output of verbose messages.

--version

Display version information then exit.

## SIGNALS
On receipt of SIGHUP virtvboxd will reload its configuration.

## FILES

### When run as root
•

/etc/libvirt/virtvboxd.conf

The default configuration file used by virtvboxd, unless overridden on the command line using the -f | --config option.

- /run/libvirt/virtvboxd-sock

- /run/libvirt/virtvboxd-sock-ro

- /run/libvirt/virtvboxd-admin-sock

The sockets virtvboxd will use.

The TLS Server private key virtvboxd will use.

•

/run/virtvboxd.pid

The PID file to use, unless overridden by the -p | --pid-file option.

### When run as non-root
•

$XDG_CONFIG_HOME/libvirt/virtvboxd.conf

The default configuration file used by virtvboxd, unless overridden on the command line using the -f``|--config`` option.

- $XDG_RUNTIME_DIR/libvirt/virtvboxd-sock

- $XDG_RUNTIME_DIR/libvirt/virtvboxd-admin-sock

The sockets virtvboxd will use.

•

$XDG_RUNTIME_DIR/libvirt/virtvboxd.pid

The PID file to use, unless overridden by the -p``|--pid-file`` option.

If $XDG_CONFIG_HOME is not set in your environment, virtvboxd will use $HOME/.config

If $XDG_RUNTIME_DIR is not set in your environment, virtvboxd will use $HOME/.cache

## EXAMPLES
To retrieve the version of virtvboxd:

```
# virtvboxd --version
virtvboxd (libvirt) 11.10.0
```

To start virtvboxd, instructing it to daemonize and create a PID file:

```
# virtvboxd -d
# ls -la /run/virtvboxd.pid
-rw-r--r-- 1 root root 6 Jul  9 02:40 /run/virtvboxd.pid
```

## BUGS
Please report all bugs you discover. This should be done via either:

1.

the mailing list https://libvirt.org/contact.html

2.

the bug tracker https://libvirt.org/bugs.html

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
virtvboxd 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://libvirt.org/daemons.html, https://libvirt.org/drvvbox.html


virtlockd

package: libvirt-daemon-lock

title: virtlockd(8)

summary: libvirt lock management daemon

text:
# virtlockd(8)

## NAME
virtlockd - libvirt lock management daemon

## SYNOPSIS
virtlockd [OPTION]...

## DESCRIPTION
The virtlockd program is a server side daemon component of the libvirt virtualization management system that is used to manage locks held against virtual machine resources, such as their disks.

This daemon is not used directly by libvirt client applications, rather it is called on their behalf by libvirtd. By maintaining the locks in a standalone daemon, the main libvirtd daemon can be restarted without risk of losing locks. The virtlockd daemon has the ability to re-exec() itself upon receiving SIGUSR1, to allow live upgrades without downtime.

The virtlockd daemon listens for requests on a local Unix domain socket.

## OPTIONS
-h, --help

Display command line help usage then exit.

-d, --daemon

Run as a daemon and write PID file.

-f, --config FILE

Use this configuration file, overriding the default value.

-t, --timeout SECONDS

Automatically shutdown after SECONDS have elapsed with no active client or lock.

-p, --pid-file FILE

Use this name for the PID file, overriding the default value.

-v, --verbose

Enable output of verbose messages.

-V, --version

Display version information then exit.

## SIGNALS
On receipt of SIGUSR1, virtlockd will re-exec() its binary, while maintaining all current locks and clients. This allows for live upgrades of the virtlockd service.

## FILES

### When run as root
•

/etc/libvirt/virtlockd.conf

The default configuration file used by virtlockd, unless overridden on the command line using the -f | --config option.

•

/run/libvirt/virtlockd-sock

The sockets virtlockd will use.

•

/run/virtlockd.pid

The PID file to use, unless overridden by the -p | --pid-file option.

### When run as non-root
•

$XDG_CONFIG_HOME/libvirt/virtlockd.conf

The default configuration file used by virtlockd, unless overridden on the command line using the -f | --config option.

•

$XDG_RUNTIME_DIR/libvirt/virtlockd-sock

The socket virtlockd will use.

•

$XDG_RUNTIME_DIR/libvirt/virtlockd.pid

The PID file to use, unless overridden by the -p | --pid-file option.

If $XDG_CONFIG_HOME is not set in your environment, virtlockd will use $HOME/.config

If $XDG_RUNTIME_DIR is not set in your environment, virtlockd will use $HOME/.cache

## EXAMPLES
To retrieve the version of virtlockd:

```
# virtlockd --version
virtlockd (libvirt) 11.10.0
```

To start virtlockd, instructing it to daemonize and create a PID file:

```
# virtlockd -d
# ls -la /run/virtlockd.pid
-rw-r--r-- 1 root root 6 Jul  9 02:40 /run/virtlockd.pid
```

## BUGS
Please report all bugs you discover. This should be done via either:

1.

the mailing list https://libvirt.org/contact.html

2.

the bug tracker https://libvirt.org/bugs.html

Alternatively, you may report bugs to your software distributor / vendor.

## AUTHORS
Please refer to the AUTHORS file distributed with libvirt.

## COPYRIGHT
Copyright (C) 2006-2013 Red Hat, Inc., and the authors listed in the libvirt AUTHORS file.

## LICENSE
virtlockd 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
libvirtd(8), https://libvirt.org/


virtlogd

package: libvirt-daemon-log

title: virtlogd(8)

summary: libvirt log management daemon

text:
# virtlogd(8)

## NAME
virtlogd - libvirt log management daemon

## SYNOPSIS
virtlogd [OPTION]...

## DESCRIPTION
The virtlogd program is a server side daemon component of the libvirt virtualization management system that is used to manage logs from virtual machine consoles.

This daemon is not used directly by libvirt client applications, rather it is called on their behalf by libvirtd. By maintaining the logs in a standalone daemon, the main libvirtd daemon can be restarted without risk of losing logs. The virtlogd daemon has the ability to re-exec() itself upon receiving SIGUSR1, to allow live upgrades without downtime.

The virtlogd daemon listens for requests on a local Unix domain socket.

## OPTIONS
-h, --help

Display command line help usage then exit.

-d, --daemon

Run as a daemon and write PID file.

-f, --config FILE

Use this configuration file, overriding the default value.

-t, --timeout SECONDS

Automatically shutdown after SECONDS have elapsed with no active console log.

-p, --pid-file FILE

Use this name for the PID file, overriding the default value.

-v, --verbose

Enable output of verbose messages.

-V, --version

Display version information then exit.

## SIGNALS
On receipt of SIGUSR1, virtlogd will re-exec() its binary, while maintaining all current logs and clients. This allows for live upgrades of the virtlogd service.

## FILES

### When run as root
•

/etc/libvirt/virtlogd.conf

The default configuration file used by virtlogd, unless overridden on the command line using the -f | --config option.

•

/run/libvirt/virtlogd-sock

The sockets virtlogd will use.

•

/run/virtlogd.pid

The PID file to use, unless overridden by the -p | --pid-file option.

### When run as non-root
•

$XDG_CONFIG_HOME/libvirt/virtlogd.conf

The default configuration file used by virtlogd, unless overridden on the command line using the -f | --config option.

•

$XDG_RUNTIME_DIR/libvirt/virtlogd-sock

The socket virtlogd will use.

•

$XDG_RUNTIME_DIR/libvirt/virtlogd.pid

The PID file to use, unless overridden by the -p | --pid-file option.

If $XDG_CONFIG_HOME is not set in your environment, virtlogd will use $HOME/.config

If $XDG_RUNTIME_DIR is not set in your environment, virtlogd will use $HOME/.cache

## EXAMPLES
To retrieve the version of virtlogd:

```
# virtlogd --version
virtlogd (libvirt) 11.10.0
```

To start virtlogd, instructing it to daemonize and create a PID file:

```
# virtlogd -d
# ls -la /run/virtlogd.pid
-rw-r--r-- 1 root root 6 Jul  9 02:40 /run/virtlogd.pid
```

## BUGS
Please report all bugs you discover. This should be done via either:

1.

the mailing list https://libvirt.org/contact.html

2.

the bug tracker https://libvirt.org/bugs.html

Alternatively, you may report bugs to your software distributor / vendor.

## AUTHORS
Please refer to the AUTHORS file distributed with libvirt.

## COPYRIGHT
Copyright (C) 2006-2015 Red Hat, Inc., and the authors listed in the libvirt AUTHORS file.

## LICENSE
virtlogd 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
libvirtd(8), https://libvirt.org/


virt-sanlock-cleanup

package: libvirt-daemon-plugin-sanlock

title: virt-sanlock-cleanup(8)

text:
# virt-sanlock-cleanup(8)

## NAME
virt-sanlock-cleanup - remove stale sanlock resource lease files

## SYNOPSIS
virt-sanlock-cleanup

## DESCRIPTION
This tool removes any resource lease files created by the sanlock lock manager plugin. The resource lease files only need to exist on disks when a guest using the resource is active. This script reclaims the disk space used by resources which are not currently active.

## EXIT STATUS
Upon successful processing of leases cleanup, an exit status of 0 will be set. Upon fatal error a non-zero status will be set.

## AUTHOR
Daniel P. Berrangé

## BUGS
Please report all bugs you discover. This should be done via either:

1.

the mailing list https://libvirt.org/contact.html

2.

the bug tracker https://libvirt.org/bugs.html

Alternatively, you may report bugs to your software distributor / vendor.

## COPYRIGHT
Copyright (C) 2011, 2013 Red Hat, Inc.

## LICENSE
virt-sanlock-cleanup is distributed under the terms of the GNU GPL v2+. 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), online instructions, https://libvirt.org/


virtproxyd

package: libvirt-daemon-proxy

title: virtproxyd(8)

summary: libvirt proxy daemon

text:
# virtproxyd(8)

## NAME
virtproxyd - libvirt proxy daemon

## SYNOPSIS
virtproxyd [OPTION]...

## DESCRIPTION
The virtproxyd 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 and

- Listens on a UNIX socket to provide backwards compatibility for clients that previously connected to the libvirtd socket.

- Optionally listens on TCP ports for connections from off-node clients

Upon receiving RPC messages from a client virtproxyd will transparently forward them on to the appropriate modular daemon, and similarly relay back any asynchronous events.

By default, the virtproxyd daemon listens for requests on a local Unix domain socket with the same path previously used by libvirtd. The configuration file can be used to instruct it to also listen on TCP socket(s). Systemd socket activation is also supported to allow it to receive pre-opened listener sockets on startup.

Since virtproxyd merely forwards RPC messages, it has no important state, and can be restarted at any time. Clients should expect to reconnect after the restart.

## DAEMON STARTUP MODES
The virtproxyd 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, 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

```
$ systemctl start virtproxyd-tls.socket
```

Or

```
$ systemctl start virtproxyd-tcp.socket
```

Note: The TCP socket uses plain unencrypted TCP connection and thus is insecure and should not be used.

### Traditional service mode
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
-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 no client connections.

-v, --verbose

Enable output of verbose messages.

--version

Display version information then exit.

## SIGNALS
On receipt of SIGHUP virtproxyd will reload its configuration.

## FILES

### When run as root
•

/etc/libvirt/virtproxyd.conf

The default configuration file used by virtproxyd, unless overridden on the command line using the -f | --config option.

- /run/libvirt/libvirt-sock

- /run/libvirt/libvirt-sock-ro

The sockets virtproxyd will use.

•

/etc/pki/CA/cacert.pem

The TLS Certificate Authority certificate virtproxyd will use.

•

/etc/pki/libvirt/servercert.pem

The TLS Server certificate virtproxyd will use.

•

/etc/pki/libvirt/private/serverkey.pem

The TLS Server private key virtproxyd will use.

•

/run/virtproxyd.pid

The PID file to use, unless overridden by the -p | --pid-file option.

### When run as non-root
•

$XDG_CONFIG_HOME/libvirt/virtproxyd.conf

The default configuration file used by virtproxyd, unless overridden on the command line using the -f``|--config`` option.

•

$XDG_RUNTIME_DIR/libvirt/libvirt-sock

The socket virtproxyd will use.

•

$HOME/.pki/libvirt/cacert.pem

The TLS Certificate Authority certificate virtproxyd will use.

•

$HOME/.pki/libvirt/servercert.pem

The TLS Server certificate virtproxyd will use.

•

$HOME/.pki/libvirt/serverkey.pem

The TLS Server private key virtproxyd will use.

•

$XDG_RUNTIME_DIR/libvirt/virtproxyd.pid

The PID file to use, unless overridden by the -p``|--pid-file`` option.

If $XDG_CONFIG_HOME is not set in your environment, virtproxyd will use $HOME/.config

If $XDG_RUNTIME_DIR is not set in your environment, virtproxyd will use $HOME/.cache

## EXAMPLES
To retrieve the version of virtproxyd:

```
# virtproxyd --version
virtproxyd (libvirt) 11.10.0
```

To start virtproxyd, instructing it to daemonize and create a PID file:

```
# virtproxyd -d
# ls -la /run/virtproxyd.pid
-rw-r--r-- 1 root root 6 Jul  9 02:40 /run/virtproxyd.pid
```

## BUGS
Please report all bugs you discover. This should be done via either:

1.

the mailing list https://libvirt.org/contact.html

2.

the bug tracker https://libvirt.org/bugs.html

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
virtproxyd 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://libvirt.org/daemons.html,


lighttpd

package: lighttpd

title: lighttpd(8)

summary: a fast, secure and flexible web server

text:
# lighttpd(8)

## NAME
lighttpd - a fast, secure and flexible web server

## SYNOPSIS
lighttpd [-ptDvVh] -f configfile [-m moduledir]

## DESCRIPTION
lighttpd (pronounced 'lighty') is an advanced HTTP daemon that aims to be secure, fast, compliant and very flexible. It has been optimized for high performance. Its feature set includes, but is not limited to, FastCGI, CGI, basic and digest HTTP authentication, output compression, URL rewriting.

This manual page only lists the command line arguments. For details on how to configure lighttpd and its modules see the files in the doc-directory.

## OPTIONS
The following options are supported:

-f configfile

Load configuration file configfile. Optionally, use -f - to read config from stdin; -f - is incompatible with -1.

-m moduledir

Use moduledir as the directory that contains modules, instead of the default.

-p

Print the parsed configuration file in its internal form and exit.

-t

Test the configuration file for syntax errors and exit.

-tt

Test the configuration file for syntax errors, load and initialize modules, and exit.

-D

Do not daemonize (go into background). The default is to daemonize.

-i secs

Trigger daemon graceful shutdown after secs of inactivity.

-1

Process single (one) request on stdin socket, then exit.

-v

Show version and exit.

-V

Show compile-time features and exit.

-h

Show a brief help message and exit.

## FILES
/etc/lighttpd/lighttpd.conf

The standard location for the configuration file.

/run/lighttpd.pid

The standard location for the PID of the running lighttpd process.

## SEE ALSO
Online Documentation: https://wiki.lighttpd.net/

spawn-fcgi(1)

Hypertext Transfer Protocol -- HTTP/1.1, RFC 2616.

HTTP Authentication: Basic and Digest Access Authentication, RFC 2617.

The Common Gateway Interface Version 1.1, RFC 3875.

The FastCGI specification.

## AUTHOR
Jan Kneschke <jan@kneschke.de>


lighttpd-angel

title: lighttpd-angel(8)

summary: monitor/supervise lighttpd daemon

text:
# lighttpd-angel(8)

## NAME
lighttpd-angel - monitor/supervise lighttpd daemon

## SYNOPSIS
lighttpd-angel <args>

## DESCRIPTION
lighttpd-angel monitors/supervises lighttpd daemon (started with <args>). lighttpd-angel will restart lighttpd if lighttpd exits for any reason, other than by signals sent by lighttpd-angel.

Send lighttpd-angel SIGTERM to initiate immediate shutdown of lighttpd.

Send lighttpd-angel SIGINT to initiate graceful shutdown of lighttpd.

Send lighttpd-angel SIGHUP to initiate graceful restart of lighttpd.

Send lighttpd-angel SIGUSR1 to initiate graceful reload of lighttpd config.

## SEE ALSO
Online Documentation:

https://wiki.lighttpd.net/InstallFromSource https://blog.lighttpd.net/articles/2007/09/02/there-is-an-angel-for-lighty/

## AUTHOR
Jan Kneschke <jan@kneschke.de>


keytab-lilo

package: lilo

title: keytab-lilo(8)

text:
# keytab-lilo(8)

## NAME
keytab-lilo - compile keytables files for use with LILO

## SYNOPSIS
/usr/sbin/keytab-lilo [-p R old_code = new_code ] ... [default_layout] kbd_layout

## DESCRIPTION
keytab-lilo is a program which compiles keytable definitions (in the format specified in keytables(5)) into a format which can be used by lilo(8) to set the keyboard type when booting [using the keytable parameter in /etc/lilo.conf].

kbd_layout should be the name of a map file which specifies the desired keyboard layout. This file may be a gzip(1) compressed map. If no file extension is given, .map.gz is assumed. If the full pathname is not specified, /usr/share/keymaps/ is assumed.

Since lilo essentially needs to know the differences between the BIOS keyboard mapping and the one you require, the default_layout file should contain a keytables(5) file for the BIOS default mapping. If no default_layout file is specified, us.map.gz is used.

keytab-lilo writes the output translation table as a binary string to standard output, so you should redirect it to a suitable file. lilo has no particular restrictions on the name of keyboard translation files, but the suggested naming convention and location is /boot/mapping.ktl (where .ktl stands for "Keyboard Table for Lilo").

## OPTIONS
-p

R old_code = new_code

Specifies corrections ("patches") to the mapping obtained from the translation table files. E.g. if pressing the upper case "A" should yield an at sign, -p 65=64 would be used. The -p option can be repeated any number of times. The codes can also be given as hexadecimal or as octal numbers if they are prefixed with 0x or 0, respectively.

## EXAMPLES
keytab-lilo dvorak >/boot/dvorak.ktl

This is the most common form of invocation; it simply compiles the given map file (in this case dvorak) and puts the result in /boot/dvorak.ktl.

## AUTHOR
Werner Almesberger (almesber@bernina.ethz.ch).

Peter Maydell (pmaydell@chiark.greenend.org.uk) wrote this manual page.

## SEE ALSO
lilo(8), keytables(5), gzip(1)


lilo

title: lilo(8)

summary: install boot loader of LiLO

text:
# lilo(8)

## NAME
lilo - install boot loader of LiLO

## SYNOPSIS
Main function:

? lilo

Auxiliary uses:

? lilo -A # activate/show active partition

? lilo -E # edit header or update a bitmap file

? lilo -I # inquire path name of current kernel

? lilo -M # write a Master Boot Loader on a device

? lilo -q # query map and show its content

? lilo -R # set default command line for next reboot

? lilo -T # tell more about specified topic

? lilo {-u|-U} # uninstall LiLO boot loader

## DESCRIPTION
lilo installs a boot loader that will be activated the next time you boot your system. The default configuration file /etc/lilo.conf (see manpage lilo.conf(5)) will contain most options, but many, including those which override the configuration file, may be specified on the command line.

## OPTIONS
-A master-device [N]

Used with a single argument, inquire of active partition on device master-device; e.g. /dev/sda. With N==0: deactivate all partitions on the device. With N in the range [1..n]: activate the specified partition and deactivate all others. Normally, only primary partitions [1..4] may be activated, but if the 'Extended Master Boot Loader' is present on the Master Boot Record (MBR) of the device (see the -M option), any partition may be made active. Whether the actual OS in the partition will boot from a logical partition depends on the characteristics of the OS. LILO boot records for Linux may be booted from a logical partition.

-b bootdev

Set the boot device where the boot loader will be installed. For example "-b /dev/sda" set the Master Boot Record (MBR) on the first disk as boot device. "-b /dev/sdb5" set the first logical partition on the second disk as boot device.

-B bitmap-file

Define a bitmap file for the boot-time graphics screen, preferably one already pre-processed with the -E option.

-c

Enable map compaction. This will merge read requests from adjacent sectors. Speeds up the booting especially from floppy.

-C config-file

Set another pathname and filename for the configuration file. The default configuration file is /etc/lilo.conf.

-d delay-time

Set the delay time in tenths of a second ('20' = 2 sec) before automatically booting the first image. This give you time to interrupt the automatic boot process with: Shift, Alt, Ctrl, ScrollLock, or CapsLock. If interrupted, the boot: prompt will be displayed. This switch will be overridden by the appearance of prompt in the configuration file!

-D label

Use the kernel with the given label as the default kernel to boot, instead of the first one in the list of the configuration file.

-E filename.xxx

If the extension .xxx is .bmp, then take the file to be a bitmap graphic file for use in the bitmap= configuration file directive. Enter an interactive editor to create or update the color/placement information in the LILO header of this bitmap file. (see bmp-colors, bmp-table, and bmp-timer on the manual page for lilo.conf (5).) If .xxx is .dat then take this file to be a configuration file to set bitmap graphic parameters, which are transferred into the LILO header in the bitmap file of the same name.

When a .bmp file is modified using a graphics editor (e.g. GIMP), the LILO header will be lost. It can be restored using the dat file, which is used as a text-based backup for the LILO header information.

-f disk-tab

Set another disk geometry parameter file. The default is /etc/disktab.

-F

Override boot sector check for filesystems (e.g., swap, ext4, xfs ...) which might be destroyed by the installation of the LILO boot sector on the first sector of the partition if these filesystems use the first sector as a superblock. Compare with -P ignore, which bypasses certain partition table checks.

-g

Generate 'cylinder/head/sector' (CHS geometric) disk addresses. Limited to cylinders up to 1023. Forces compatibility with very old versions of LILO (obsolete switch).

-H

Override fatal halt if a RAID array does not have all disks active.

-I label [D|a|i|k|r|R]

label is taken to be the name of an image specified in the configuration file. This command will print the path name of the corresponding kernel file, keytable file, initial ramdisk file, root specification, or "append=" string ("i", "k", "r", "R", or "a" option). The "D" option ignores the label parameter and prints the default "image=" label, or the first "image=" label is selected if no default image is set.

-l

Generate 24-bit linear sector addresses instead of cylinder/head/sector addresses.

-L

Generate 32-bit Logical Block Addresses (LBA) instead of cylinder/head/sector (CHS) addresses, allowing access to all partitions on disks with more than 1024 cylinders. (This is the default geometry).

-m map-file

Use another map file instead of the default file /boot/map.

-M master-device {mbr|ext}

Install a Master Boot Record on the device specified as master-device, selecting the Standard or Extended Master Boot Loader per option. The primary partition table on master-device is undisturbed. If no valid Volume-ID (serial number) is present, then generate one and write it to the MBR. If mbr is set, the Standard Master Boot Loader will search partitions 1-4 for an active flag, and boot the flagged partition. Only one active flag is allowed. If ext is set, the search for an active partition will include logical partitions as well. The presence of the Extended Master Boot Loader on the Master Boot Record (MBR = sector 0) of a disk affects the operation of the -A option.

-p

Require interactive entry of all passwords set as "" in the configuration file.

-P {fix|ignore|<global-option}>

Fix or ignore 'corrupt' partition tables, e.g. partition tables with linear and cylinder/head/sector addresses that do not correspond. Always try ignore first, as fix will re-write the partition table, possibly destroying all partitions on the disk. ignore is also used to bypass the partition table check for partition types within the partition table which might not allow the installation of a LILO boot sector. Compare with the '-F' flag, which overrides the check of the actual boot sector.

<global-option> allows the passing of any global option which may appear in the global section (top) of the configuration file (/etc/lilo.conf). For instance '-P nowarn' will pass the 'nowarn' option, just as though 'nowarn' appeared in the configuration file (same as the '-w' switch). Similarly '-P timeout=50' will add or override the 'timeout=' line in the configuration file. Note that the general -P switch actually duplicates a number of command line option switches. However, it is not strictly the same as some switches which cause an override of other options; e.g. '-g' (-P geometric), '-L' (-P lba32).

-q

List the currently mapped files. lilo maintains a file, by default /boot/map, containing each name and location of the kernel(s) to boot. This option will list the names therein. Use with -v for more detailed information about the installed boot loader.

-r root-directory

Before doing anything else, do a 'chroot' to the indicated directory. The new root directory must contain a /dev directory and may need a /boot directory. It may also need an /etc/lilo.conf file.

-R command-line

This option sets the default command for the boot loader for the next time it executes. After execution the boot loader will erase this line because it is a once-only command. It is typically used in reboot scripts, just before calling 'shutdown -r'. Used without any arguments, it will cancel a lock-ed or fallback command line. This Command line starts with image identifier (as shown during map file update), then space, then kernel parameters. The kernel parameters are appended to kernel command line constructed routinely. In either case, it there were parameters or not, such one-time command will be treated by loaders code, as if it is set at 'boot:' prompt. This could lead to 'password:' prompt at boot time. Be warned! Refer to lilo.conf(5) for details.

-s save-file

When lilo writes a new boot sector, it preserves the former contents of the boot sector in a file, named by default /boot/boot.NNNN, where NNNN is the hexadecimal representation of the major and minor device numbers of the drive/partition. This option defines the backup save file in one of three ways: a save directory (default is '/boot') using the default filename 'boot.NNNN' in the defined directory; a pathname template to which '.NNNN' is appended (default would be '/boot/boot'); or the full pathname of the file, which must include the correct '.NNNN' suffix. When used with the -u option, the full file pathname must be set.

-S save-file

Normally lilo will not overwrite an existing boot sector save file. This options says that overwriting is to be forced. As with -s, the setting may be of a save directory, pathname template, or full pathname (which includes the '.NNNN' suffix).

-t

Test only. Do not really write a new boot sector or map file. Use together with -v to find out what lilo is about to do.

-T option

Print out system information, some of it extracted from system bios. This is more convenient than booting the LILO diagnostic floppy on problem systems. option may be any one of the following:

```
 help          print a list of available diagnostics
 ChRul         list the partition types subject to
                 Change-Rules
 EBDA          list Extended BIOS Data Area information
 geom=<drive>  list drive geometry for bios drive;
                 e.g. geom=0x80
 geom          list drive geometry for all drives
 table=<drive> list the primary partition table;
                 e.g. table=/dev/sda
 video         list graphic modes available to boot
                 loader

```

-u [device-name]

Uninstall lilo by copying the saved boot sector back. The -s and -C switches may be used with this option. The device-name is optional. A time-stamp is checked.

-U [device-name]

The same as '-u', but do not check the time-stamp.

-v [number]

Increase verbosity. Giving one to five -v options will make lilo more verbose. The number (range 1..5) set verbosity level.

-V

Print version number.

-w[+|-]

Used as -w or -w- to suppress warning messages. Used as '-w+' to override 'nowarn' in the configuration file and show warning messages.

-x option

For RAID installations only. The option may be any of the keywords: none, auto, mbr, mbr-only, or a comma separated list of additional boot devices (no spaces allowed in the list). RAID installations write the boot record to the RAID partition. Conditional writing of MBRs may occur to aid in making the RAID set bootable in a recovery situation, but all default actions may be overridden. Action similar to previous versions is achieved using the '-x mbr-only' switch.

-X

Reserved for LILO internal use. May produce different output for different LILO versions. The line beginning "CFLAGS=" will contain the compiler options used to generate this version of LILO.

-z

When used with the '-M' switch, clears the Volume-ID. Usually used in the following sequence to generate a new Volume-ID:

```
    lilo -z -M /dev/sda
    lilo -M /dev/sda

```

-Z option

Tells the boot installer whether special precautions need to be taken because the BIOS fails to pass the correct device code in DL (-Z0). Or may specify that the BIOS always gets DL right (-Z1). Corresponds to, and overrides, the configuration file option 'bios-passes-dl='.

## CONFIG OPTIONS
The above command line options correspond to the key words in the config file indicated below.

```
              -b bootdev       boot=bootdev
              -B file.bmp      bitmap=file.bmp
              -c               compact
              -d dsec          delay=dsec
              -D label         default=label
              -f file          disktab=file
              -g               geometric
              -l               linear
              -L               lba32
              -m mapfile       map=mapfile
              -P fix           fix-table
              -P ignore        ignore-table
              -s file          backup=file
              -S file          force-backup=file
              -v [N]           verbose=N
              -w               nowarn
              -x option        raid-extra-boot=option
              -Z option        bios-passes-dl=option
```

## BOOT OPTIONS
The options described here may be specified at boot time on the command line when a kernel image is booted. These options are processed by LILO, and are removed from the command line before it is passed to the kernel, unless otherwise noted.

lock

Locks the command line, as though 'lock' had been defined in /etc/lilo.conf.

mem=###[,K,M,G]

Set the maximum memory in the system in bytes, kilobytes, megabytes or gigabytes. This option is not removed from the command line, and is always passed to the kernel.

nobd

Suppresses the BIOS data check. This option is reserved for use with non-IBM-compliant BIOS's which hang with the lines:

```
    Loading...............
    BIOS data check

```

vga=[ASK,EXT,EXTENDED,NORMAL,###,0x###]

Allows overriding the default video mode upon kernel startup.

## BOOT ERRORS
The boot process takes place in two stages. The first stage loader is a single sector, and is loaded by the BIOS or by the loader in the MBR. It loads the multi-sector second stage loader, but is very space limited. When the first stage loader gets control, it types the letter 'L'; when it is ready to transfer control to the second stage loader it types the letter 'I'. If any error occurs, like a disk read error, it will put out a hexadecimal error code and then re-try the operation. All hex error codes are BIOS return values, except for the lilo-generated codes: 40, 99 and 9A. A partial list of error codes follows:

```
    00  no error
    01  invalid disk command
    02  address mark not found
    03  disk write-protected
    04  sector not found
    06  floppy disk removed
    08  DMA overrun
    0A  bad sector flag
    0B  bad track flag
    20  controller failure
    40  seek failure (BIOS)
    40  cylinder>1023 (LILO)
    99  invalid second stage index sector (LILO)
    9A  no second stage loader signature (LILO)
    AA  drive not ready
    FF  sense operation failed
```

Error code 40 is generated by the BIOS, or by LILO during the conversion of a linear (24-bit) disk address to a geometric (C:H:S) address. On older systems which do not support lba32 (32-bit) addressing, this error may also be generated. Errors 99 and 9A usually mean the map file ('-m' or 'map=') is not readable, likely because LILO was not re-run after some system change, or there is a geometry mismatch between what LILO used (lilo -v3 to display) and what is actually being used by the BIOS (one of the lilo diagnostic disks, available in the source distribution, may be needed to diagnose this problem).

When the second stage loader has received control from the first stage, it prints the letter 'L', and when it has initialized itself, including verifying the "Descriptor Table" - the list of kernels/others to boot - it will print the letter "O", to form the full word "LILO", in uppercase.

All second stage loader error messages are English text and try to pinpoint, more or less successfully, the point of failure.

## BUGS
Configuration file options 'backup' and 'force-backup' should specify a backup directory or backup file pathname template on all RAID installations. Use of an explicit filename may not allow multiple backup files to be created correctly. It is best to use the default mechanism, as it works correctly in all cases.

## COPYRIGHT and LICENSE

```
 Copyright (C) 1992-1998 Werner Almesberger
 Copyright (C) 1999-2007 John Coffman
 Copyright (C) 2009-2014 Joachim Wiedorn
```

Redistribution and use in source and binary forms, with or without modification, are permitted under the terms of the BSD license found in the COPYING file.

## AUTHOR
lilo was written by:

```
 Werner Almesberger (version 0 to 21),
 John Coffman (version 21.2 to 22.8),
 Joachim Wiedorn (since version 23.0).
```

This manual page was written by Werner Almesberger and Joachim Wiedorn <joodevel at joonet.de>.

## SEE ALSO
lilo.conf(5), liloconfig(8), lilo-uuid-diskid(8), mkrescue(8), fdisk(8), mkinitrd(8)


lilo-uuid-diskid

title: lilo-uuid-diskid(8)

text:
# lilo-uuid-diskid(8)

## NAME
lilo-uuid-diskid - convert boot / root options to diskid and uuid in lilo.conf.

## SYNOPSIS
lilo-uuid-diskid [-h] [-v] [lilo.conf]

## DESCRIPTION
This script looks for the boot block device or boot partition and create the right diskid or uuid as boot option. Then it looks for all root partitions and create the right uuids as root options.

These conversions are necessary for use with newer kernel (>= 2.6.26) if it use the libata module for parallel and serial ATA interfaces of block devices (i. e. hard disks with IDE or SATA interface, usbsticks).

## OPTIONS
-h

Print a brief help.

-v

Print verbose messages.

## EXAMPLES
Lines in the configuration file /etc/lilo.conf:

```
  #boot = /dev/sda
  boot = /dev/disk/by-id/ata-SAMSUNG_SV1604N_S01FJ10X999999
  #root = /dev/sda1
  root = "UUID=18843936-00f9-4df0-a373-000d05a5dd44"
```

## COPYRIGHT and LICENSE
Copyright (C) 2010-2014 Joachim Wiedorn

This script is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.

## AUTHOR
lilo-uuid-diskid was written by Joachim Wiedorn.

This manual page was written by Joachim Wiedorn <joodevel at joonet.de>.

## SEE ALSO
lilo(8), update-lilo(8), liloconfig(8)


liloconfig

title: liloconfig(8)

text:
# liloconfig(8)

## NAME
liloconfig - create new lilo.conf file (with diskid and uuid)

## SYNOPSIS
liloconfig [-h] [-v] [-f] [-u] [lilo.conf]

## DESCRIPTION
liloconfig is an simple program for creating a new lilo.conf file. After creating the new configuration file you must execute '/sbin/lilo'.

liloconfig use the lilo.example.conf file as template. In the final lilo.conf file you find many useful comments for custom changes.

Please pay attention about error messages if liloconfig cannot find any images (/boot/vmlinuz*) oder image symlinks (/vmlinuz, /vmlinu.old). Then you need to search for images by ourself and make some changes in the '/etc/lilo.conf' file. Otherwise no bootloader can be installed with '/sbin/lilo'.

## OPTIONS
-h

Print a brief help.

-v

Print verbose messages.

-f

Force overriding existing lilo.conf.

-u

Force overriding/update of boot line in lilo.conf.

## EXAMPLES
Lines in the configuration file /etc/lilo.conf:

```
  ### LILO global section ###
  #large-memory
  lba32
  #boot = /dev/sda
  boot = /dev/disk/by-id/ata-SAMSUNG_SV1604N_S01FJ10X999999
  #root = /dev/sda1
  root = "UUID=18843936-00f9-4df0-a373-000d05a5dd44"
  map = /boot/map
  install = menu
  menu-scheme = Wb:Yr:Wb:Wb
  prompt
  timeout = 100
  vga = normal
  #password =
  #default = Linux
  ### LILO per-image section ###
  image = /boot/vmlinuz-3.17-trunk-686
      label = "Linux"
      #root = /dev/sda1
      #root = "UUID=18843936-00f9-4df0-a373-000d05a5dd44"
      read-only
  #   restricted
  #   alias = 1
  #   optional
      initrd = /boot/initrd.img-3.17-trunk-686
  image = /boot/vmlinuz-3.14-trunk-686
      label = "Linux Old"
      #root = /dev/sda1
      #root = "UUID=18843936-00f9-4df0-a373-000d05a5dd44"
      read-only
  #   restricted
  #   alias = 2
  #   optional
      initrd = /boot/initrd.img-3.14-trunk-686
```

## COPYRIGHT and LICENSE
Copyright (C) 2011-2015 Joachim Wiedorn

This script is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.

## AUTHOR
liloconfig was written by Joachim Wiedorn.

This manual page was written by Joachim Wiedorn <joodevel at joonet.de>.

## SEE ALSO
lilo(8), update-lilo(8), lilo-uuid-diskid(8)


mkrescue

title: mkrescue(8)

summary: make rescue floppy or CD

text:
# mkrescue(8)

## NAME
mkrescue - make rescue floppy or CD

## SYNOPSIS
/sbin/mkrescue makes a bootable rescue floppy or CD using the default kernel specified in lilo.conf.

## DESCRIPTION
mkrescue takes its specifation for the kernel from the default image specified in /etc/lilo.conf. If the actual default is an other= specification, then use the first image= specification. Any associated initial ramdisk (initrd=), and append= options will also be used. The root directory will be taken to be the current root. A bootable floppy or CD-image will be created using LILO version 22.5.5 or later. mkrescue normally requires no options, unless a CD-image is desired (--iso).

## OPTIONS
--append <string>

Override any append= options taken from the default image. If there is any doubt about whether the lilo.conf options are correct, then specify no kernel parameters by providing the null string (--append "").

--debug

Provide verbose output of the operation of mkrescue, pausing to allow the setting of internal operating parameters to be viewed. <CR> must be hit to proceed from these pauses.

--device <device>

Make the floppy on a device other than /dev/fd0. The floppy disk will always be made to boot on BIOS device code 0x00 (A: drive), without regard to the drive on which it is created.

--fast

Use a faster method of creating the boot floppy. This involves first creating a file of --size 1k blocks (default is 1440) mounted using a loopback device, creating the bootable floppy, then copying the entire file to the disk.

--fs [ ext2 | msdos | minix ]

Specify the type of filesystem to create on the drive. ext2 is the default, but msdos and minix allow slightly more disk sectors for really big kernels.

--help

Print a short usage synopsis, including a list of command options.

--image <label>

Specifies the label or alias of the particular image from which the append, initial ramdisk, root, keytable, and kernel information is to be taken.

--initrd <filepath> and --kernel <filepath>

These options, which must be used together, allow specification of an arbitrary kernel file and initial ramdisk file to be used on the created boot floppy. Be sure you know what you are doing before you use these options. If no inital ramdisk is needed with a particular kernel, then you MUST specify --initrd "", meaning a null pathname.

--install [ text | menu ]

Allows overriding the default human interface used with the rescue bootloader (configuration file "install=" option). text is the default on 1.2MB and 1.44MB floppy disks, and menu is the default on 2.88MB floppies and HD emulation on CD-R media.

--iso

Create an ISO-9660 bootable CD image (El Torito Format) suitable for burning to a CD-R or CD-RW. The --device specification defaults to the filename rescue.iso, and the --size defaults to 2880. A utility such as "wodim" may be used to burn the ISO file to a recordable CD medium. With this ISO option, the --size HD option is allowed.

--nocompact

For faster kernel loading from a floppy, LILO map compaction is normally enabled. This option will disable map compaction by omitting the lilo -c switch.

--noformat

Suppresses creation of a new filesystem on the boot floppy. This option may be used ONLY when you know that the floppy you will be writing upon is formatted with the same filesystem as specified by --fs XXX (default is ext2).

--root <device>

Specify the root filesystem for the kernel on the boot floppy. The currently mounted root is taken as the default specification.

--size [ 1440 | 1200 | 2880 | HD ]

The default floppy disk size is 1440, meaning a 1.44MB floppy. When --iso is specified, the default size is 2880. Allowed specifications are 1200, 1440, or 2880, meaning a 1.2MB, 1.44MB or 2.88MB floppy, respectively. No other floppy disk sizes are supported. The HD specification, meaning "hard disk", may only be used with the --iso option, to indicate a 16MB hard disk is to be generated for emulation. This allows for very large kernel/initial ramdisk combinations on CD-R. The hard disk image is created using loopback devices /dev/loop0 and /dev/loop1, which must be free to utilize this size option.

--version

Print the version number of mkrescue, then terminate.

## SEE ALSO
cdrecord(1), dd(1), wodim(1), lilo.conf(5), lilo(8), mkfs(8), mkinitrd(8), mkisofs(8), mount(8)


atmaddr

package: linux-atm

title: atmaddr(8)

summary: list and maintain local ATM addresses

text:
# atmaddr(8)

## NAME
atmaddr - list and maintain local ATM addresses

## SYNOPSIS
atmaddr [-n] [itf]

atmaddr -r [itf]

atmaddr -a [itf] atm_addr

atmaddr -d [itf] atm_addr

atmaddr -V

## DESCRIPTION
atmaddr is used to list the local addresses configured for ATM interfaces and to manually change the list of addresses. If the interface number itf is omitted, interface 0 is used by default. The ATM address atm_addr can be any valid ATM SVC address, e.g. an E.164 address or an ATM Forum NSAP address.

If invoked without options, atmaddr lists the addresses that are currently configured on the specified interface.

Note that local ATM addresses are normally automatically maintained by the ILMI demon.

## OPTIONS
-a

append the specified address at the end of the list.

-d

delete the specified address from the list.

-n

numeric address output only. No address to name translation is attempted.

-r

reset (clear) the local address list of the specified interface.

-V

print the version number of atmaddr on standard output and exit.

## AUTHOR
Werner Almesberger, EPFL ICA <Werner.Almesberger@epfl.ch>

## SEE ALSO
ilmid(8)


atmarp

title: atmarp(8)

text:
# atmarp(8)

## NAME
atmarp - administer classical IP over ATM connections

## SYNOPSIS
atmarp -a

atmarp -c [[atm]number]

atmarp -q ip_addr [qos qos] [sndbuf bytes]

atmarp -s ip_addr [itf.]vpi.vci [qos qos] [sndbuf bytes] [temp] [pub] [null]

atmarp -s ip_addr atm_addr [qos qos] [sndbuf bytes] [temp] [pub] [arpsrv]

atmarp -d ip_addr [arpsrv]

atmarp -V

## DESCRIPTION
atmarp is used to maintain the ATMARP table of the ATMARP demon. The table can be listed, new PVC and SVC entries can be added, and existing entries can be deleted. In addition to that, atmarp is also used to create new IP over ATM interfaces.

Note that the kernel has its own ATMARP table containing only entries for destinations to which a connection exists. The table of atmarpd can also contain currently unused entries.

## OPTIONS
-a

list the current ATMARP table.

-c

create the specified IP interface. If the interface number is omitted, the operating system assigns the next free number and atmarp prints the resulting interface name (e.g. `atm0') on standard output.

-q

sets the QOS and the send buffer size to use as the default for all VCs generated for that IP network (ip_addr must be the address of the network).

-s

set up a PVC or create an SVC entry. The following options are recognized:

qos qos

uses the specified quality of service (see qos(7) for the syntax). UBR at link speed is used by default.

sndbuf bytes

tries to set the send buffer to the specified number of bytes. A system default value is used if sndbuf is not specified.

temp

does not mark the entry as permanent, i.e. it will time out and then be removed.

pub

publishes the entry (only relevant for ATMARP server). ATMARP requests for entries not marked for publishing yield an ATMARP_NAK response.

null

uses NULL encapsulation instead of LLC/SNAP encapsulation on the PVC. This option is not available for SVCs, because the LLC/SNAP header is required to identify ATMARP packets. null also implies that the entry is permanent.

arpsrv

identifies the entry pointing to the ATMARP server. Note that the node acting as the ATMARP server must have no ATMARP server entry in its ATMARP table.

-d

delete the specified ARP entry. In order to prevent accidental deletion of the ATMARP server entry, the arpsrv flag must be specified when deleting it.

-V

print the version number of atmarp on standard output and exit.

## FILES
/var/run/atmarpd.table

ATMARP table

## AUTHOR
Werner Almesberger, EPFL ICA <Werner.Almesberger@epfl.ch>

## SEE ALSO
atmarpd(8), clip(8), qos(7)