VIRTSTORAGED(8)
π VIRTSTORAGED(8) π
Ok so real talk, bestie: this is the manual page for virtstoraged, a daemon that lives in the Virtualization Support section of your man pages and is very much a whole vibe in the libvirt universe. Buckle up, we're getting into it. π
β¨ NAME β¨
virtstoraged β the libvirt storage pool management daemon, aka the girl who handles your storage pools so you don't have to π
β¨ SYNOPSIS β¨
virtstoraged [OPTION]...
β¨ DESCRIPTION β¨
So virtstoraged is a server side daemon component of the libvirt virtualization management system. Iconic. Fr fr.
She's one of a whole collection of modular daemons that replaced the functionality that used to be provided by the monolithic libvirtd daemon β think of it like the friend group splitting the group project so nobody has to do everything alone π«Ά
This daemon runs on virtualization hosts and provides management for storage pools. That's literally her whole job and she ate.
Here's the important bit: virtstoraged only listens for requests on a local Unix domain socket. Remote access via TLS/TCP, plus backwards compatibility for legacy clients that still expect libvirtd, is provided by the virtproxyd daemon β that's a different girl's department, iykyk.
Now, restarting virtstoraged does not interrupt running guests. Guests keep operating, 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 β like, it's fine, but don't make it a hobby, you know? π
β¨ DAEMON STARTUP MODES β¨
The virtstoraged daemon is capable of starting in two modes. Two! Main character energy, honestly π
Socket activation mode
On hosts with systemd, it starts in socket activation mode and 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. Like, they're just there. Vibing. Ignored π
Traditional service mode
On hosts without systemd, she'll create and listen on UNIX sockets herself. Independent queen behavior β¨
β¨ OPTIONS β¨
-h,--helpβ Display command line help usage then exit. Your girl is helpful π-d,--daemonβ Run as a daemon & write PID file.-f,--configFILE β Use this configuration file, overriding the default value.-p,--pid-fileFILE β Use this name for the PID file, overriding the default value.-t,--timeoutSECONDS β Exit after timeout period (in seconds), provided there are no client connections.-v,--verboseβ Enable output of verbose messages. She'll tell you everything π£οΈ--versionβ Display version information then exit.
β¨ SIGNALS β¨
On receipt of SIGHUP, virtstoraged will reload its configuration. One little signal and she's refreshed and rejuvenated, skincare-routine style πΈ
β¨ 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
virtstoragedwill 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 β a little peek at her birth chart, if you will β
# virtstoraged --version
virtstoraged (libvirt) 12.8.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
See? She's there. She's living her life. She has a PID file. Slay π
β¨ BUGS β¨
Please report all bugs you discover. This should be done via either:
- the mailing list
https://libvirt.org/contact.html
- the bug tracker
Alternatively, you may report bugs to your software distributor / vendor.
No gatekeeping β if you found a bug, say something! π
β¨ 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. Like, literally none. Zero. Don't come for her if it breaks π
β¨ SEE ALSO β¨
virsh(1), libvirtd(8), https://libvirt.org/daemons.html, https://libvirt.org/storage.html
π That's the whole page bestie, go configure your storage pools, you've got this π«Ά
Ok that's a wrap! This was VIRTSTORAGED(8) from the Virtualization Support corner of your manual, and honestly? She understood the assignment. Mwah ππ
π¦ where this page comes from
- centos-stream 10: libvirt-daemon-driver-storage-core 12.8.0-1.el10 Β· GPL-2.0-or-later AND LGPL-2.1-only AND LGPL-2.1-or-later AND OFL-1.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms