Lima v2.2: Windows guests and TPM 2.0 emulation

Lima v2.2 adds Windows guest support, extending the path started in v2.1 when macOS and FreeBSD guests arrived. With this release, one limactl workflow can boot Linux, macOS, FreeBSD, and Windows virtual machines. The CNCF Blog presents the release as the next large step after those earlier guest types.

On the technical side, the headline capabilities are Windows guests and TPM 2.0 emulation. That combination matters because many Windows images and licensing or security features expect a TPM-backed environment; emulating TPM 2.0 is what makes a usable Windows guest path practical rather than a partial demo. The control plane stays limactl, so guest OS choice becomes configuration of the same tool rather than a separate stack.

For engineers and builders, the value is consolidation. Teams that already use Lima for Linux (and, since v2.1, macOS or FreeBSD) can keep the same CLI and automation patterns when a Windows VM is required for builds, drivers, desktop QA, or mixed-OS CI. Fewer hypervisors and scripts mean less drift between local, laptop, and pipeline environments.

In market and tooling context, Lima sits in the lightweight local-VM niche popular with container and cloud-native developers. Supporting Linux, macOS, FreeBSD, and Windows under one workflow narrows the gap where people previously jumped to platform-specific tools for Windows while keeping Lima (or similar) for Unix-like guests. Publication on the CNCF Blog also signals relevance to the cloud-native audience that already treats limactl as day-to-day infrastructure.

Practical takeaway: if your workflows still split Windows elsewhere, try routing that guest through limactl on v2.2 and check that TPM-dependent steps (attestation, secure boot expectations, or product install paths) behave as needed. Watch how the Windows guest path holds up under real images and automation, and whether TPM 2.0 emulation covers the scenarios you actually run—not only bare boot.

Next signal to watch is adoption feedback on Windows plus TPM 2.0 in daily use, especially whether teams standardize on a single limactl matrix for all four guest families rather than keeping a parallel Windows-only toolchain.