Colima instance getting unresponsive when using Virtualization.framework alongside other VMs

### Description

Hi all. I am experiencing a weird issue where colima instance (using Virtualization.framework) is getting stuck and unresponsive while reporting a Running state. This happens on the machines where we run other Virtualization.framework VMs, 2 macOS virtual machines to be precise:
```
~ % colima ls
PROFILE STATUS ARCH CPUS MEMORY DISK RUNTIME ADDRESS
default Running aarch64 2 2GiB 60GiB docker
~ % colima status
FATA[0003] error retrieving current runtime: empty value
~ % colima ssh
FATA[0006] exit status 255
~ % docker ps
Cannot connect to the Docker daemon at unix:///Users/master/.colima/default/docker.sock. Is the docker daemon running?
```

One of the suspicion was a memory pressure, so I have limited other VMs to keep 4 spare GiB (total) of host memory, yet it still happening. While I am trying to find a way to consistently reproduce this, would love to hear some opinions and suggestions on what can I try to avoid having this issue at all.

Thanks.

### Version

colima version 0.6.9
git commit: c3a31ed05f5fab8b2cdbae835198e8fb1717fd0f
limactl version 0.22.0
qemu-img version 9.0.1

### Operating System

- [ ] macOS Intel <= 13 (Ventura)
- [ ] macOS Intel >= 14 (Sonoma)
- [ ] Apple Silicon <= 13 (Ventura)
- [X] Apple Silicon >= 14 (Sonoma)
- [ ] Linux

### Output of `colima status`

~ % colima status
FATA[0003] error retrieving current runtime: empty value

### Reproduction Steps

1. Run 2 macOS VMs using Virtualization.framework alongside colima using Virtualization framework.
2. Use all available CPU and All available memory -4 GiB by macOS VMs.
3. Utilize macOS VMs with some performance job.
4. Colima will be stuck eventually, but not consistently. Happens on a big scale with different machines.

### Expected behaviour

Colima instance not being stuck or at least report some resource pressure for debugging.

### Additional context

_No response_