Colima v0.5.5 Regression | error dialing "192.168.5.15:22": connect tcp 192.168.5.15:22: no route to host

BlissChapman commented 1 year ago

Description

On Colima v0.5.4, this command works great: colima start --memory 4 --vm-type=vz --vz-rosetta

On Colima v0.5.5 (and HEAD), this same command fails with the following error:

Colima start --memory 4 --vm-type=vz --vz-rosetta
INFO[0000] starting colima                              
INFO[0000] runtime: docker                              
INFO[0000] starting ...                                  context=vm
> [hostagent] Setting up Rosetta share
> SSH Local Port: 56482
> [hostagent] [VZ] - vm state change: running
> [hostagent] Waiting for the essential requirement 1 of 3: "ssh"
> [hostagent] Waiting for the essential requirement 1 of 3: "ssh"
> [hostagent] 2023/08/27 20:26:03 tcpproxy: for incoming conn 127.0.0.1:56486, error dialing "192.168.5.15:22": connect tcp 192.168.5.15:22: no route to host

Version

% colima version

colima version HEAD-afe81c4
git commit: afe81c4334e62d405dc94869ed1d85dc950345e2

runtime: docker
arch: aarch64
client: v23.0.5
server: v20.10.20

% limactl --version

limactl version 0.17.2

% qemu-img --version

qemu-img version 8.0.4
Copyright (c) 2003-2022 Fabrice Bellard and the QEMU Project developers

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/blisschapman/.colima/default/docker.sock

Reproduction Steps

Install colima@v0.5.5.
Run colima start --memory 4 --vm-type=vz --vz-rosetta
Observe error.
Install colima@v0.5.4 or download the released artifact.
Run colima start --memory 4 --vm-type=vz --vz-rosetta using the 0.5.4 binary.
Observe colima starts without error.

Expected behaviour

colima start --memory 4 --vm-type=vz --vz-rosetta works on top of tree.

Additional context

No response

BlissChapman commented 1 year ago

Updating my machine to Ventura 13.5.1 has resolved this issue on my local machine. Will leave this ticket open for the maintainers to decide if they want that solution to be the recommended resolution.

javathought commented 1 year ago

For me, the issue raised after upgrading to Ventura 13.5.1 (macOS M2)

Version

colima version 0.5.5
git commit: 6251dc2c2c5d8197c356f0e402ad028945f0e830

runtime: docker
arch: aarch64

limactl version 0.17.2
qemu-img version 8.1.0

Output of colima status

FATA[0003] error retrieving current runtime: empty value

which is strange, runtime has disappeared in colima list result too, but few steps before was present.

I deleted the profile and restarted new one and it's ok

abiosoft / colima