Lima VM on macOS Sonoma does not start after 4 successful create & start

[evanNyew]

Description

I am running lima with socket_vmnet and bootptab provides the ip-addresses. After restarting the configuration 4 or 5 times, the entire lima vm facility become effectively inoperable. I am able to create the vm, but they won't not start. I tried reinstall both lima, socket_vmnet, restart dhcp, reboot machine. I have made sure the sudoers are in sync. I am running out of ideas of what may be causing this.
Any suggestion are welcome!

Here is logs from ha.stderr.log {"level":"debug","msg":"Mixing \"/Users/evannyew/.lima/_config/override.yaml\" into \"/Users/evannyew/.lima/test0/lima.yaml\"","time":"2023-10-13T16:54:42+07:00"} {"level":"debug","msg":"Mixing \"/Users/evannyew/.lima/_config/override.yaml\" into \"/Users/evannyew/.lima/test0/lima.yaml\"","time":"2023-10-13T16:54:42+07:00"} {"level":"debug","msg":"Creating iso file /Users/evannyew/.lima/test0/cidata.iso","time":"2023-10-13T16:54:43+07:00"} {"level":"debug","msg":"Using /var/folders/9b/pht96fh535ng9kfvm13362tc0000gn/T/diskfs_iso657063647 as workspace","time":"2023-10-13T16:54:43+07:00"} {"level":"debug","msg":"Failed to detect CPU features. Assuming that AES acceleration is available on this Apple silicon.","time":"2023-10-13T16:54:44+07:00"} {"level":"debug","msg":"OpenSSH version 9.3.2 detected","time":"2023-10-13T16:54:44+07:00"} {"level":"debug","msg":"AES accelerator seems available, prioritizing aes128-gcm@openssh.com and aes256-gcm@openssh.com","time":"2023-10-13T16:54:44+07:00"} {"level":"info","msg":"Starting VZ (hint: to watch the boot progress, see \"/Users/evannyew/.lima/test0/serial*.log\")","time":"2023-10-13T16:54:44+07:00"} {"level":"debug","msg":"Start tcp DNS listening on: 127.0.0.1:49343","time":"2023-10-13T16:54:44+07:00"} {"level":"debug","msg":"Start udp DNS listening on: 127.0.0.1:58622","time":"2023-10-13T16:54:44+07:00"} {"level":"info","msg":"new connection from to ","time":"2023-10-13T16:54:44+07:00"} {"level":"debug","msg":"Using socketVMNet (\"/opt/homebrew/Cellar/socket_vmnet/1.1.3/bin/socket_vmnet\")","time":"2023-10-13T16:54:44+07:00"} {"level":"fatal","msg":"dial unix /private/var/run/lima/socket_vmnet.shared: connect: connection refused","time":"2023-10-13T16:54:44+07:00"}

[AkihiroSuda]

• Do you see something in ~/.lima/<INSTANCE>/serial*.log?
• Does limactl start --video show some error in the video screen?
• Is this issue specific to socket_vmnet? Does it work if you disable socket_vmnet ?

[madalinignisca]

For me the {"level":"fatal","msg":"dial unix /private/var/run/lima/socket_vmnet.shared: connect: connection refused","time":"2023-10-13T16:54:44+07:00"} happens when I making mistakes in the shared network entry.

Ensure that the shared network entry in your networks.yml is good and it will work.