Skip to navigationSkip to content
libvirtd docs
Commands

Manual nav

Search `/` or jump with `g` / `G`.

Portal

  • Home manual
  • Command explorer
Foundations6 sections
  • Overview1
  • Installation2
  • Platform1
  • Concepts5
  • Domains2
  • Domain XML2
Subsystems9 sections
  • Identity1
  • Automation2
  • Daemons3
  • virsh3
  • Networking5
  • Storage4
  • Security3
  • Observability2
  • Remote Access1
Operations6 sections
  • Migration2
  • Backup2
  • Performance3
  • Recovery1
  • Troubleshooting2
  • References2

/ search · g top · G quickstart

manstorageReviewed March 6, 2026

Storage pools and backends

Libvirt pools abstract where guest disks live. The pool type tells you which backend owns the bytes and which operational failure modes to expect. Common pool types | Type | What it maps to | Operational note | | | | | |

storage pooldirlvmnfsiscsi

Libvirt pools abstract where guest disks live. The pool type tells you which backend owns the bytes and which operational failure modes to expect.

Common pool types

TypeWhat it maps toOperational note
dirA filesystem directorySimplest to inspect and back up
logicalLVM volume groupFast and common for dense local hosts
netfsNFS exportShared storage with external network dependency
iscsiiSCSI targetBlock storage with network path and initiator state

Pool lifecycle

BASH
virsh pool-list --all
virsh pool-info fast-lvm
virsh pool-dumpxml fast-lvm
virsh vol-list fast-lvm

What to read first

  • For dir, inspect the directory path, ownership, and mount state.
  • For LVM, inspect the volume group and free extents.
  • For NFS, confirm the mount is live before blaming libvirt.
  • For iSCSI, verify the session and device visibility on the host.

Safety checks

Never assume a pool that is defined is also started, mounted, or healthy.

Related

  • Pool and volume workflows
  • Troubleshooting playbook
  • Files, sockets, and service units

On this page

  • Common pool types
  • Pool lifecycle
  • What to read first
  • Safety checks