2 , we added support for Windows guests. On November 6, we shipped v2. 3 of Lima and now it runs without extra dependencies on Windows: VMs start through the same Host Compute System that powers WSL2, without QEMU and without a Unix toolchain. On Linux, VMs are getting the " real IP address" networking that Mac users have had through ` socket_vmnet `. And on every host, managing your VMs gets friendlier with a new terminal UI . Lima (Linux Machines) is a command-line tool to launch local virtual machines.

Originally focused on running containers on a laptop and promoting containerd to Mac users, Lima joined the CNCF as a Sandbox project in September 2022 and was promoted to Incubating in October 2025. Today, Lima supports a wide variety of non-container workloads, non-macOS hosts, non-Linux guests and robust AI sandboxing. If you are on Windows, Lima can be installed through PowerShell using: For other installation methods, see https://lima-vm. Until now, Windows users who wanted Lima had two options: the ` wsl2 ` or QEMU driver. 3 adds a third, the new ` hcs ` driver .

It talks directly to the Windows Host Compute System (HCS) API, the Windows virtualization layer that WSL2 is built on. 2 announcement, we said that our LFX mentorship would "explore and evaluate native virtualization support for Windows hosts". A few weeks later, that research has become a working driver. On macOS, ` socket_vmnet ` gives VMs an IP address that the host can reach directly. Linux had no equivalent, so the ` lima: shared `, ` lima: host ` and ` lima: bridged ` networks only worked on macOS.

3 introduces ` lima-privileged-net `, a small privileged helper for Linux hosts which: Creating bridges and tap devices requires root, so there are two steps before your first start: With v2. 3, Lima can now attach a block device (USB drive or an external SSD) to VZ guests, without going through a file share. In order for this feature to work, sudo privileges are required to configure it. Opening a host disk requires root, so there are two steps before your first `-block-device` start: 2.