Control plane, drivers, and execution plane

Libvirt 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

virsh / application
        |
libvirt client API
        |
UNIX socket, SSH, or TLS
        |
libvirtd or modular daemon
        |
QEMU, network, storage, secret, and node-device drivers
        |
kernel KVM + host resources

This separation explains why a successful API connection does not prove a guest can boot. Socket access, XML validation, storage labels, bridge state, QEMU capabilities, and KVM acceleration are distinct gates.

Ask the right layer

• Use virsh uri and socket inspection for connection failures.
• Use virsh domstate, dumpxml, and QEMU logs for domain failures.
• Use net-dumpxml, ip, and firewall tooling for network failures.
• Use pool-info, vol-info, and filesystem evidence for storage failures.