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

manrecoveryReviewed July 3, 2026

SSH, IPMI, and ZFS Recovery Order

Recovery sequence The fastest recovery path is rarely the loudest one. Start with SSH if the host is still reachable and telemetry suggests userland or service failure. Move to IPMI or equivalent out of band control when

sshipmizfsrecovery

Recovery sequence

The fastest recovery path is rarely the loudest one. Start with SSH if the host is still reachable and telemetry suggests userland or service failure. Move to IPMI or equivalent out-of-band control when you need console truth or a hard power boundary. Bring ZFS investigation in only after the control path is stable enough to observe the storage layer without compounding corruption risk.

Operator guidance

  1. Confirm whether SSH still provides trustworthy state.
  2. Use IPMI when you need console reality, boot visibility, or safe remote power control.
  3. Treat ZFS as a storage recovery discipline, not the first response to every platform incident.
  4. Record the regain-of-control order in the handoff notes once the incident is stabilized.

Related

  • Remote TLS, TCP, and auth basics
  • Troubleshooting playbook

On this page

  • Recovery sequence
  • Operator guidance