v2.1.0-rc.1Pre-releasemacOSLinux
Added 8
- Support macOS guests with limactl start template:macos
- Support FreeBSD guests with limactl start template:freebsd
- Add limactl watch command
- Add limactl shell --sync to prevent AI agents from breaking the host files
- Add limactl (create|edit|start) --nested-virt as an alias for --set '.nestedVirtualization = true'
- Support nested virtualization in krunkit
- Add host-to-guest time synchronization
- Restore debian-11 template
Changed 5
- Guest home directory changed from /home/${USER}.linux to /home/${USER}.guest with old path symlinked for compatibility
- Use QEMU by default for non-native architectures
- Reduce guestagent binary footprint from 14M to 6.1M
- Consolidate basedisk and diffdisk into a single disk file for efficiency
- k3s template now supports creating multi-node clusters
🎉 Highlights:
- Support macOS guests:
limactl start template:macos - Support FreeBSD guests:
limactl start template:freebsd - Add
limactl shell --syncto prevent AI agents from breaking the host files
Changes
-
Guest OS support:
- Experimentally support macOS guests (#4595)
- Experimentally support FreeBSD guests (#4627)
-
limactlCLI:- Add
limactl watchcommand (#4489, thanks to @IrvingMg) - Add
limactl shell --syncto prevent AI agents from breaking the host files (#4429, thanks to @unsuman) - Add
limactl (create|edit|start) --nested-virtas an alias for--set '.nestedVirtualization = true'(#4663)
- Add
-
Guest home directory:
- The guest home directory is changed from
/home/${USER}.linuxto/home/${USER}.guest(#4578). For compatibility, the old path is symlinked to the new one.
- The guest home directory is changed from
-
QEMU:
- Use QEMU by default for non-native architectures (#4725)
-
krunkit:
- Support nested virtualization (#4658, thanks to @abiosoft)
-
Hostagent:
- Add host-to-guest time synchronization (#4527, thanks to @mfenderov)
-
Guestagent:
- Reduce binary footprint (14M -> 6.1M) (#4120, #4536)
-
Internal file structure:
basediskanddiffdiskare consolidated into a singlediskfile for efficiency (#4587, thanks to @jandubois). No impact is expected for end users. An instance created with Lima v2.0 or v1.x should continue to boot with Lima v2.1 (but not vice versa).
-
Templates:
k3s: support creating multi-node clusters (#4505, thanks to @afbjorklund)- Restore
debian-11(#4574, thanks to @olamilekan000)
-
Project:
- MAINTAINERS: promote Norio Nomura (@norio-nomura) to a Committer (#4511)
Full changes: https://github.com/lima-vm/lima/milestone/62?closed=1 @Harry-kp @IrvingMg @TatsuyaHayashino @abiosoft @afbjorklund @alexandear @arixmkii @bmwiedemann @hekki @jandubois @majiayu000 @mfenderov @ningmingxiao @norio-nomura @olamilekan000 @tharunn0 @tushar1977 @unsuman
Usage
$ limactl create
$ limactl start
...
INFO[0029] READY. Run `lima` to open the shell.
$ lima uname
Linux
The binaries were built automatically on GitHub Actions. The build log is available for 90 days: https://github.com/lima-vm/lima/actions/runs/23115903481
The sha256sum of the SHA256SUMS file itself is 90f5f673101d51e1f1b4c219d883a34b389cea5fb3f0d65b4b2944b96def4015 .
Release manager: @AkihiroSuda