Description
Lima template:experimental/ubuntu-26.04 picks up the OS image from https://cloud-images.ubuntu.com/resolute/current/
The images available there were dated February 2026 and worked fine with limactl start. On 2026-03-28, Ubuntu 26.04 switched from an alpha to beta release in that download URL, which makes Lima VM boot get stuck forever in a Waiting for port to become available on 192.168.5.15:22 loop, as shown below.
I don't know if this is simply a glitch in the Ubuntu beta that will be rectified in the final Ubuntu release, or an intended breaking change, or possibly something that Lima could (or should?) work around somehow. I'm reporting it here just FYI, and in the hope that anyone might have more insight how to best get this fixed eventually.
Here is what still works today:
$ limactl --version
limactl version 2.1.0
$ uname -a
Darwin MacBook-Pro.local 24.6.0 Darwin Kernel Version 24.6.0: Mon Jan 19 21:56:28 PST 2026; root:xnu-11417.140.69.708.3~1/RELEASE_ARM64_T6020 arm64
$ limactl --tty=false create --name=mylimavm template:ubuntu-25.10; limactl --tty=false start --progress=true --log-level=debug mylimavm
<This works fine>
$ limactl delete --force mylimavm
Here is how template:experimental/ubuntu-26.04 nomore works after the 2026-03-28 update:
$ limactl --tty=false create --name=mylimavm template:experimental/ubuntu-26.04; limactl --tty=false start --progress=true --log-level=debug mylimavm
INFO[0000] Terminal is not available, proceeding without opening an editor
INFO[0000] Attempting to download the image arch=aarch64 digest= location="https://cloud-images.ubuntu.com/resolute/current/resolute-server-cloudimg-arm64.img"
INFO[0000] Using cache "/Users/foo/Library/Caches/lima/download/by-url-sha256/ecfbe382d6cd7377cad5019591dc0c9579cc094058d17620bded9b7dd648571e/data"
INFO[0002] Run `limactl start mylimavm` to start the instance.
DEBU[0000] interpreting argument "mylimavm" as an instance name
INFO[0000] Using the existing instance "mylimavm"
DEBU[0000] Make sure "user-v2" network is stopped
DEBU[0000] Make sure usernet network is stopped
DEBU[0000] Make sure "shared" network is stopped
DEBU[0000] Make sure "bridged" network is stopped
DEBU[0000] Make sure "host" network is stopped
INFO[0000] Starting the instance "mylimavm" with internal VM driver "vz"
DEBU[0000] Using internal driver "vz"
INFO[0000] [hostagent] time="2026-03-31T16:11:58-04:00" level=debug msg="Plugin discovery: failed to scan directory /Users/foo/bin: open /Users/foo/bin: no such file or directory"
INFO[0000] [hostagent] time="2026-03-31T16:11:58-04:00" level=debug msg="Plugin discovery: failed to scan directory /Users/foo/.pyenv/bin: open /Users/foo/.pyenv/bin: no such file or directory"
INFO[0000] [hostagent] time="2026-03-31T16:11:58-04:00" level=debug msg="Plugin discovery: failed to scan directory /usr/local/opt/nethogs/sbin: open /usr/local/opt/nethogs/sbin: no such file or directory"
INFO[0000] [hostagent] time="2026-03-31T16:11:58-04:00" level=debug msg="Plugin discovery: failed to scan directory /usr/local/opt/git/bin: open /usr/local/opt/git/bin: no such file or directory"
INFO[0000] [hostagent] time="2026-03-31T16:11:58-04:00" level=debug msg="Plugin discovery: failed to scan directory /var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin: open /var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin: no such file or directory"
INFO[0000] [hostagent] time="2026-03-31T16:11:58-04:00" level=debug msg="Plugin discovery: failed to scan directory /var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin: open /var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin: no such file or directory"
INFO[0000] [hostagent] time="2026-03-31T16:11:58-04:00" level=debug msg="Plugin discovery: failed to scan directory /var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin: open /var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin: no such file or directory"
INFO[0000] [hostagent] time="2026-03-31T16:11:58-04:00" level=debug msg="Plugin discovery: failed to scan directory /Applications/VMware Fusion.app/Contents/Public: open /Applications/VMware Fusion.app/Contents/Public: no such file or directory"
INFO[0000] [hostagent] time="2026-03-31T16:11:58-04:00" level=debug msg="Plugin /opt/homebrew/Cellar/lima/2.1.0/libexec/lima/limactl-mcp: not a script file, skipping description extraction"
INFO[0000] [hostagent] time="2026-03-31T16:11:58-04:00" level=debug msg="Plugin limactl-url-fedora-rawhide: no <limactl-desc> found in script"
DEBU[0000] [hostagent] Using internal driver "vz"
DEBU[0000] [hostagent] Decompressing /opt/homebrew/share/lima/lima-guestagent.Linux-aarch64.gz
DEBU[0000] [hostagent] Creating iso file /Users/foo/.lima/mylimavm/cidata.iso
DEBU[0000] [hostagent] Using /var/folders/dj/y5mjnplj0l79dq4dkknbsjbh0000gp/T/diskfs_iso94304234 as workspace
DEBU[0000] [hostagent] Failed to detect CPU features. Assuming that AES acceleration is available on this Apple silicon.
DEBU[0000] [hostagent] OpenSSH version 9.9.2 detected, is GSSAPI supported: true
DEBU[0000] [hostagent] AES accelerator seems available, prioritizing aes128-gcm@openssh.com and aes256-gcm@openssh.com
INFO[0000] [hostagent] hostagent socket created at /Users/foo/.lima/mylimavm/ha.sock
DEBU[0000] [hostagent] Start udp DNS listening on: 127.0.0.1:50642
INFO[0000] [hostagent] Starting VZ (hint: to watch the boot progress, see "/Users/foo/.lima/mylimavm/serial*.log")
DEBU[0000] [hostagent] Start tcp DNS listening on: 127.0.0.1:55725
DEBU[0000] [hostagent] Kernel file "/Users/foo/.lima/mylimavm/kernel" not found
DEBU[0000] [hostagent] Using EFI Boot Loader
DEBU[0000] [hostagent] new connection from to
DEBU[0000] [hostagent] [VZ] - vm state change: "VirtualMachineStateStarting"
INFO[0000] [hostagent] [VZ] - vm state change: running
DEBU[0002] [hostagent] Waiting for port to become available on 192.168.5.15:22
DEBU[0003] [hostagent] Waiting for port to become available on 192.168.5.15:22
DEBU[0004] [hostagent] Waiting for port to become available on 192.168.5.15:22
...
same 'Waiting for port to become available' repeating forever.
Description
Lima template:experimental/ubuntu-26.04 picks up the OS image from https://cloud-images.ubuntu.com/resolute/current/
The images available there were dated February 2026 and worked fine with
limactl start. On 2026-03-28, Ubuntu 26.04 switched from an alpha to beta release in that download URL, which makes Lima VM boot get stuck forever in aWaiting for port to become available on 192.168.5.15:22loop, as shown below.I don't know if this is simply a glitch in the Ubuntu beta that will be rectified in the final Ubuntu release, or an intended breaking change, or possibly something that Lima could (or should?) work around somehow. I'm reporting it here just FYI, and in the hope that anyone might have more insight how to best get this fixed eventually.
Here is what still works today:
Here is how template:experimental/ubuntu-26.04 nomore works after the 2026-03-28 update:
same 'Waiting for port to become available' repeating forever.