Skip to content
libvirtd(8) manual
Commands
Confidential / Operator Copy / Field Manual
LIBVIRTD(8)

Linux Infrastructure Operating Manual

libvirtd.com

A living manual for Linux infrastructure, virtualization, platform operations, identity, automation, and operator discipline.

Written for operators who prefer durable systems, explicit handoffs, secure defaults, and commands that still make sense during an outage.

NAMESYNOPSISDESCRIPTIONOPTIONSFILESEXAMPLESWARNINGSSEE ALSO
SectionLIBVIRTD(8)
ClassOperator field manual
ScopeLinux, identity, automation
ReleaseBRIDGE_SITE_RELEASE=1.1

NAME

libvirtd.com

libvirtd.com - living manual for Linux infrastructure, identity, automation, and platform operations.

The site borrows its shape from manual pages because production infrastructure rewards clarity over theater: name the thing, describe the interfaces, show the options, preserve the files, and leave enough evidence for the next operator.

SYNOPSIS

Invocation patterns

libvirtd --platform linux --identity freeipa --automation puppet --remote sshlibvirtd --operate --document --harden --handofflibvirtd --baseline rhel --publish apache --secure tls --store postgresql

DESCRIPTION

Operating discipline

libvirtd.com documents the discipline behind Linux platform operations: building hosts that can be rebuilt, identity systems that can be explained, automation that reduces drift, and procedures that survive personnel changes.

It treats documentation as part of the system. A platform is not complete when it works once; it is complete when another qualified operator can understand it, repair it, audit it, and safely hand it forward.

OPTIONS

Domain flags

--linux-platform
Operate RHEL-family systems, Fedora workstations, RPM lifecycle patterns, systemd units, host baselines, and patch discipline.
--identity
Design and maintain FreeIPA, LDAP, Kerberos, Okta, SCIM, SAML, OIDC, host enrollment, and account lifecycle controls.
--automation
Use Puppet, Foreman, Satellite, provisioning standards, and repeatable configuration to reduce drift and make change reviewable.
--remote-systems
Work through SSH-first administration, recovery sessions, out-of-band access, storage awareness, and server room constraints.
--application-platforms
Support Apache HTTPD, TLS, PostgreSQL, Linux services, platform dependencies, and service handoff patterns.
--security-governance
Keep GitHub Enterprise, access reviews, repository controls, policy boundaries, and audit-friendly decisions close to daily operations.
--documentation
Write operational records that map intent, commands, ownership, recovery paths, and inheritance boundaries.

FILES

Known paths

/etc/libvirtd/operator

Primary manual surface and operational reference root.

/var/lib/libvirtd/profile

Stateful records, incident memory, and recovery sequences.

/usr/share/doc/libvirtd/bridge

Bridge-adjacent documentation layer for deeper operator records.

/opt/bridge/christopher-jones

Deliberately buried record reachable by path-aware readers.

/docs/observability/field-activity

Weekly field activity console and regional pulse archive.

Some records are intentionally filed below the obvious layer. Operators who need the map will read the paths.

EXAMPLES

Operator sessions

libvirtd deploy --rhel --baseline --selinux

Provision a host baseline that preserves service ownership, package intent, and policy controls before higher layers land.

libvirtd identity --freeipa --okta --scim

Map human approval, directory authority, and Linux enforcement into one lifecycle path instead of multiple disconnected systems.

libvirtd automate --puppet --foreman --satellite

Use control loops that make state reviewable, repairable, and consistent across inherited infrastructure.

libvirtd publish --apache --tls --postgresql

Document the service edge, certificate path, and backing data-plane before rollout so the system can be handed forward.

libvirtd recover --ssh --ipmi --zfs

Sequence remote access, out-of-band control, and storage recovery in the order most likely to regain the host without compounding failure.

WARNINGS

Operator cautions

Do not treat identity, automation, and recovery as separate disciplines when inheriting Linux estates.
Do not disable SELinux or relax policy controls before reading ownership, labels, service context, and daemon boundaries.
Do not mistake documentation for theory: every reference should support operational handoff under pressure.

SEE ALSO

Adjacent manuals

freeipa(1), sshd_config(5), puppet(8), foreman(8), httpd(8), postgres(1)

World activity captureWeekly visitor telemetry in an operator-style console.Operator drillsShort training surfaces that reveal deeper reference paths.Identity boundariesMixed-authority lifecycle patterns for Linux identity estates.Automation control loopsHow Puppet and Foreman reduce drift and preserve reviewable change.Recovery orderSSH, out-of-band control, and storage recovery sequencing.freescim.comAdjacent work centered on identity lifecycle control.
Overview1 docsInstallation2 docsPlatform1 docs