# Install terraform-provider-libvirt with Homebrew Terraform provisioning with Linux KVM using libvirt. Version 0.9.8 via Homebrew; verified 2026-07-26. ## Install ```sh sudo av install brew:terraform-provider-libvirt ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install terraform-provider-libvirt ``` Evidence: local Homebrew formula metadata ## Package facts - **Package key:** brew:terraform-provider-libvirt - **Package manager:** Homebrew - **Version:** 0.9.8 - **Source summary:** Terraform provisioning with Linux KVM using libvirt - **Homepage:** - **Repository:** - **Last updated:** 2026-07-26T00:50:36+02:00 - **Generated:** 2026-08-03T19:37:03+00:00 ## Executables - terraform-provider-libvirt (alias) ## Install behavior - Bottle: not available ## Freshness - Page generated: 2026-08-03 - Package-manager version: 0.9.8 ## Project history and usage terraform-provider-libvirt is a Terraform provider for managing local or remote libvirt virtualization resources such as virtual machines, networks, storage pools, and volumes. ### Project history The project dates to February 2016, making it one of the older community Terraform providers for local virtualization. Its purpose is to let Terraform manage Linux KVM/libvirt infrastructure through provider resources rather than ad hoc shell scripts or virt-manager workflows. The current README describes v0.9.0 and later as a complete rewrite of the legacy provider. The legacy v0.8 branch remains available, while the rewritten provider is built on the Terraform Plugin Framework and models libvirt XML schemas more directly through libvirtxml. ### Adoption history The provider has long occupied a practical niche for homelab, workstation, CI, and private-cloud users who want Terraform workflows without a public cloud control plane. The GitHub repository has a large star count for a community provider, and Homebrew packages current releases as a convenient way to install the provider binary outside Terraform's normal provider installer paths. Its documentation now points users to both the Terraform Registry and the OpenTofu registry, reflecting the post-Terraform-fork packaging world where provider consumers may use either registry ecosystem. ### How it is used Users declare `dmacvicar/libvirt` as a required provider and configure a libvirt URI such as `qemu:///system`, `qemu+ssh://.../system`, `qemu+sshcmd://.../system`, or `qemu+tls://.../system`. The provider then manages domains, networks, pools, and volumes using HCL that maps closely to libvirt XML. The README also documents local development installation under `~/.terraform.d/plugins/registry.terraform.io/dmacvicar/libvirt/dev/linux_amd64/` with a Terraform CLI dev override, which matters to packagers and provider developers testing local builds. ### Why package nerds care For package nerds, terraform-provider-libvirt is a classic non-cloud Terraform provider with awkward packaging edges: it is both a Terraform registry provider and a Homebrew formula, depends on libvirt concepts, and bridges the Terraform provider installation model with local virtualization workflows. ### Timeline - 2016: GitHub repository created. - 2026: v0.9.x releases continue the rewritten Terraform Plugin Framework provider line. - 2026: Homebrew packages v0.9.8. ### Related projects - libvirt, KVM, and QEMU are the virtualization stack managed by the provider. - Terraform Registry and OpenTofu Registry are the documented provider distribution surfaces. ### Sources - - - - ## Security Notes infrastructure mutation or orchestration signal. - **Geiger risk:** orange / medium - infrastructure mutation or orchestration signal ## Combined YAML source View the package source record on GitHub. [combined/terraform-provider-libvirt.yml](https://github.com/mxcl/pkgdb/blob/main/combined/terraform-provider-libvirt.yml) ## Sources - pkg.so package database - Geiger risk classifier - curated package history - pkgdb category and tag curation - cross-ecosystem install command graph