Intermittent freezing of vm on M1+Ventura while using DDEV fixed with Link-Local Only IPv6 setting on Mac

[siliconmeadow]

Description

After upgrading to Ventura 13.2.1 and 13.3, my colima vm would intermittently freeze - not responding to any ddev commands, nor colima status. After issuing any ddev or colima command and waiting several minutes, I would do a ctrl-c to get the terminal back.

Searching through the issue queue, I found this post and in particular this comment where it's mentioned:

Under Mac, I went to my network, selected the interface, goto TCP/IP settings and set "Configure IPv6" to "Link-Local Only" - reboot and it is now working!

I did the same with my Macbook - I changed the settings via the Mac's network gui so that IPv6 was set to Link-Local Only and the intermittent freezing seems to have disappeared.

Version

Colima Version: HEAD-65ee3d2 Lima Version: 0.15.0 Qemu Version: 7.2.0 (although I'm using --vm-type vz)

Operating System

• [ ] macOS Intel <= 12 (Monterrey)
• [ ] macOS Intel >= 13 (Ventura)
• [ ] macOS M1 <= 12 (Monterrey)
• [X] macOS M1 >= 13 (Ventura)
• [ ] Linux

Output of colima status

INFO[0000] colima is running using macOS Virtualization.Framework INFO[0000] arch: aarch64 INFO[0000] runtime: docker INFO[0000] mountType: virtiofs INFO[0000] socket: unix:///Users//.colima/default/docker.sock

Reproduction Steps

1. colima start --cpu 4 --memory 8 --vm-type vz
2. Start a ddev project with ddev start
3. Visit local ddev site started in previous step and do normal development tasks via the browser and using ddev drush *
4. In the space of three minutes to an hour, eventually the site stops responding, and entering ddev and colima commands stick indefinitely and eventually need killing with a ctrl-c.
5. Only a killall limactl seems to allow resumption, although it means doing a colima start and beginning again.

Expected behaviour

I would expect that the environment created by colima to continue to function reliably for an indefinite period.

Additional context

As I don't have a specific need for IPv6 at the moment, and my Mac seems to be fine with IPv6 being configured as Link-Local Only, I'm happy with that as a solution and possibly for it to be a long term solution. Perhaps there is absolutely nothing wrong with Colima, and there is something weird going on with MacOS.

This might be a helpful solution to others.

[raphaelcosta]

The same issue happened for me and changing the IPv6 configuration did work.

[rfay]

I just had the hangup; had to colima stop -f and then kill off lima processes before changing Link-Local.

[abiosoft]

Thanks for this. I believe this only happens when using --vm-type vz, right?

[rfay]

@abiosoft no, I'm using QEMU:

$ colima status
INFO[0000] colima is running using QEMU
INFO[0000] arch: aarch64
INFO[0000] runtime: docker
INFO[0000] mountType: sshfs
INFO[0000] socket: unix:///Users/rfay/.colima/default/docker.sock

[abiosoft]

@abiosoft no, I'm using QEMU

Thanks for the information. I should probably add this to the troubleshooting FAQ until we find a fix.

[raphaelcosta]

@abiosoft I got the same issue with VZ, the fix also worked.

$ colima status
INFO[0000] colima is running using macOS Virtualization.Framework
INFO[0000] arch: aarch64
INFO[0000] runtime: docker
INFO[0000] mountType: virtiofs

[ia3andy]

Same problem here, the fix worked

[rfay]

I've changed the DDEV docs to recommend VZ/VirtioFS in latest DDEV docs.

[ia3andy]

Ahh I spoke too fast, it's still freezing for me..

[ia3andy]

in my case it's not with DDev, but the issue seems to be the same...