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

manobservabilityReviewed July 15, 2026

Logs, events, and long-running job state

Good diagnosis correlates the API request, daemon journal, QEMU domain log, and current job state on one timeline. Follow state changes Read the owning service Build useful evidence Capture UTC timestamps, URI, domain UU

journalctleventsdomjobinfologs

Good diagnosis correlates the API request, daemon journal, QEMU domain log, and current job state on one timeline.

Follow state changes

BASH
virsh event --all --loop
virsh domstate guest01 --reason
virsh domjobinfo guest01 --completed

Read the owning service

BASH
journalctl -u libvirtd -u virtqemud -u virtproxyd --since -30m
journalctl _COMM=virtqemud --since -30m
tail -n 200 /var/log/libvirt/qemu/guest01.log

Build useful evidence

Capture UTC timestamps, URI, domain UUID, operation, caller identity, source and target host, job statistics, and final state. Avoid logging private keys, authentication tokens, full secret XML, or guest data.

Related

  • virtqemud and virtproxyd roles
  • Field Activity and Weekly Capture
  • Guest start failure: evidence-first triage

On this page

  • Follow state changes
  • Read the owning service
  • Build useful evidence