Files, sockets, and service units
This page is the quick lookup table for the names operators tend to forget during an incident. Common systemd units | Unit | Purpose | | | | | libvirtd.service | Historical compatibility daemon | | libvirtd.socket | Comp
This page is the quick lookup table for the names operators tend to forget during an incident.
Common systemd units
| Unit | Purpose |
|---|---|
libvirtd.service | Historical compatibility daemon |
libvirtd.socket | Compatibility socket entry point |
virtqemud.service | QEMU domain management |
virtqemud.socket | Socket activation for QEMU domain management |
virtproxyd.service | Compatibility proxy daemon |
virtproxyd.socket | Local proxy socket |
virtproxyd-tls.socket | TLS listener for remote clients |
Compatibility units
libvirtd.service and libvirtd.socket are the historical compatibility names. They may still exist even when the real work happens in modular daemons.
QEMU units
virtqemud.service and virtqemud.socket own QEMU domain operations on modular hosts.
Remote listener units
virtproxyd.socket and virtproxyd-tls.socket are the units to inspect when remote or compatibility clients can connect but real operations still fail.
Common filesystem locations
/etc/libvirt/
/etc/libvirt/qemu/
/var/lib/libvirt/images/
/run/libvirt/
/var/log/libvirt/One command that helps a lot
systemctl list-unit-files "virt*" "libvirtd*"That single command often tells you more than manually checking one guessed unit name at a time.