VIRTNETWORKD(8)

πŸ¦‹ VIRTNETWORKD(8) πŸ¦‹

Okay bestie, welcome to the Virtualization Support manual page for virtnetworkd. The header line is folded in right here, and yes, we’re doing this with full group-chat energy. πŸ’…

🌸 NAME 🌸

virtnetworkd β€” libvirt virtual network management daemon. Periodt. πŸ’–

✨ SYNOPSIS ✨

virtnetworkd [OPTION]...

πŸŽ€ DESCRIPTION πŸŽ€

So virtnetworkd is a server side daemon component of the libvirt virtualization management system. It’s one of a collection of modular daemons that replace functionality previously provided by the monolithic libvirtd daemon. The way that works? This daemon runs on virtualization hosts to provide management for virtual networks. πŸ¦‹

It 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. Iykyk. πŸ”₯

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. Vibe check:

πŸ”Œ 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. Not me being useless config-wise β€” that’s just how it is. πŸ’€

🧚 Traditional service mode 🧚

On hosts without systemd, it will create and listen on UNIX sockets itself. Main character energy: it handles its own sockets. ✨

πŸ’… 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. That’s the signal tea. 🫢

πŸŽ€ 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

Those last three are 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

Those are 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. (Yes, .cache β€” that’s what the page says, bestie. No cap.) πŸ“

πŸ“ EXAMPLES πŸ“

To retrieve the version of virtnetworkd:

# virtnetworkd --version
virtnetworkd (libvirt) 12.8.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 (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 πŸ¦‹

πŸ’– That’s the whole VIRTNETWORKD(8) page from the Virtualization Support manual, bestie β€” source/version/date weren’t printed separately in the copy I got, so I’m not inventing any. Mwah! πŸ’…βœ¨

πŸ“¦ where this page comes from