DOSSIER 28 / 3 ARTICLES
Advanced KVM capabilities and platform choices
Design recoverable configurations around devices, firmware, image chains, and management tools.
Start with the first articleFollow the question further.
Build advanced foundations with UEFI/TPM, VFIO, virtiofs, and offline image chains, then explore declarative NixOS hosts and desktop, web, and IaC tool choices. Keep external runtime state and resource-ownership boundaries explicit.
- 01
Examine the independent state of UEFI/TPM and VFIO first, then read CPU/I/O tuning, virtiofs, and offline image chains as needed.
KVM firmware, VFIO, virtiofs, and image chains
Explain advanced parameters and document compatibility and recovery requirements for passthrough, image changes, and shared directories.
Read article - 02
Check options against the project-pinned nixpkgs, paying attention to QEMU runtime identity, firmware migration, network activation, and recovery generations.
Declaring KVM host capabilities on NixOS
Configure libvirt through version-pinned module interfaces while managing networking, firmware, and VM runtime state outside the configuration.
Read article - 03
Read architecture diagrams and resource ownership first, then compare tools by operational scope. Verify templates, credentials, and provider versions in automation examples.
Choosing KVM management and automation tools
Compare desktop, web, and automation tools, distinguishing libvirt frontends, independent platforms, and offline image building.
Read article