SEE ALSO
Related virtualization manuals
The next man pages, commands, and libvirt subsystems worth opening.
section 13 / 14
manual group: virtualization support
living notes: enabled
deep links: enabled
Reference core
verify upstream ↗virsh(1), virt-install(1), virt-xml-validate(1), virt-top(1), virt-df(1)
libvirtd OverviewWhat libvirtd is, where libvirt sits in the virtualization stack, and how the daemon model evolved.Host & InstallationKVM readiness, libvirt packages, virtualization capabilities, socket units, and first validation.Architecture & ConceptsLibvirt APIs, drivers, connection URIs, sockets, QEMU/KVM boundaries, and system versus session mode.DaemonsClassic libvirtd plus modular daemons including virtqemud, virtproxyd, virtnetworkd, and virtstoraged.virshConnection handling, domain lifecycle, inspection, console access, and day-to-day libvirt commands.DomainsVirtual-machine definitions, lifecycle states, autostart, consoles, snapshots, and guest-agent behavior.Domain XMLCPU, memory, disks, interfaces, firmware, devices, metadata, validation, and safe persistent edits.Virtual NetworkingLibvirt NAT, bridges, routed and isolated networks, DHCP, forwarding, and network diagnostics.Virtual StorageStorage pools, volumes, qcow2/raw images, backends, attachment, allocation, and storage diagnostics.Virtualization SecuritysVirt, SELinux/AppArmor, polkit, DAC ownership, secrets, TLS, and libvirt access-control boundaries.Remote libvirtRemote connection URIs, SSH, TLS, TCP listeners, authentication, virtproxyd, and transport diagnostics.MigrationLive and offline guest migration, compatibility preflight, storage constraints, transport, and rollback.Snapshots & BackupExternal snapshots, block jobs, guest quiescing, backup chains, restore testing, and recovery points.PerformancevCPU topology, NUMA, huge pages, virtio, I/O tuning, memory behavior, and virtualization contention.TroubleshootingSocket failures, domain startup errors, QEMU logs, networking, storage, permissions, and diagnostic order.Referencelibvirtd options, service units, socket paths, configuration files, command lookup, and related manuals.
Upstream libvirtd manual →Living manual · why this matters
Where should you go after libvirtd(8)?
The daemon manual is only the control-plane entry point. Real virtualization work quickly crosses into virsh, connection URIs, QEMU/KVM, domains, XML, virtual networking, storage, security, migration, snapshots and modular daemons. This page is the junction rather than the end of the manual.
Operator checks
$ virsh help$ virsh uri$ virsh capabilities$ virsh list --allWhat to notice
- Choose the next manual based on the failing or changing layer.
- The command explorer is better for verb-first lookup; subsystem docs are better for concept-first learning.
- Labs provide browser-only rehearsal without executing commands on a real host.
Deep reference
Keep going without losing the layer.
Architecture & 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 wArchitecture & ConceptsQEMU, KVM, and libvirt: division of responsibilityKVM provides kernel virtualization, QEMU models the machine and devices, and libvirt supplies a stable management contract around both. Component roles | Layer | Primary responsibility | | | | | KVM | CPU and memory virt