NAME
libvirtd — libvirt management daemon
The canonical name and one-line purpose of the traditional libvirt daemon.
section 01 / 14
manual group: virtualization support
living notes: enabled
deep links: enabled
Reference core
verify upstream ↗libvirtd — libvirt management daemon.
Living manual · why this matters
Why does one daemon name deserve its own manual?
Because libvirtd names the traditional monolithic control daemon, not the hypervisor itself. Knowing that boundary prevents a common category error: QEMU/KVM executes guests; libvirt provides the management contract; libvirtd is one server-side implementation of that contract.
Operator checks
$ command -v libvirtd$ libvirtd --version$ virsh version$ virsh uriWhat to notice
- The daemon name and the libvirt project name are related but not interchangeable.
- A host may use modular daemons instead of a running libvirtd process.
- The connection URI tells you more about the active management path than the process name alone.
Deep reference
Keep going without losing the layer.
libvirtd Overviewlibvirtd overview and the modern daemon modellibvirtd is the traditional monolithic server side daemon for the libvirt virtualization management system. It accepts libvirt client requests and coordinates the drivers that manage virtual machines and related virtualiArchitecture & ConceptsControl plane, drivers, and execution planeLibvirt is an API and driver framework. It normalizes lifecycle, storage, network, and host operations while hypervisors such as QEMU/KVM perform guest execution. Request path This separation explains why a successful APArchitecture & ConceptsFingerprint the libvirt Daemon TopologyDo not infer the active libvirt control plane from the distribution name or installed packages. Use the daemon topology decoder to classify observed systemd socket evidence before restarting a service. Classic monolithicArchitecture & ConceptsModular daemons contextLibvirt split the historical all in one daemon into smaller services so each subsystem could be isolated, restarted, and permissioned more cleanly. Why libvirt split the daemon The monolithic daemon handled many unrelateArchitecture & ConceptsOperator Change RehearsalAn operator rehearsal turns a proposed command into a reviewable state transition. Use the interactive rehearsal before a consequential libvirt change to expose missing evidence without touching a daemon. Establish the cArchitecture & ConceptsOperator Training DrillsWhy drills exist The interactive surfaces in this manual are not puzzles for their own sake. They are short operator drills. Their job is to reinforce ordering, command composition, and dependency awareness in the same w