lima-vm / lima-vm/lima

Stuck waiting for ssh -- tcpproxy no route

Open
#1,293 17 comments 4 reactions 0 assignees View on GitHub
component/vz
Dominant language
Go
Stars
21.9k
Forks
957
Avg merge
2d 6h
Merged PRs (30d)
53

Description

### Description

Hello,

I'd been working with a VM and then lost access to it. Doing `limactl stop && limactl start ` didn't seem to help, and now it just gets stuck indefinitely `Waiting for the essential requirement 1 of 3: "ssh"`.

Interestingly, this line repeats:

```
INFO[0004] [hostagent] 2023/01/11 21:51:42 tcpproxy: for incoming conn 127.0.0.1:52962, error dialing "192.168.5.15:22": connect tcp 192.168.5.15:22: no route
```

Which seems to me like maybe there's a problem with the bridge interface.

The VM template I'm using looks like this:

```
# experimental settings
vmType: vz
mountType: virtiofs
networks:
- vzNAT: true

# make it a native M1 VM
arch: aarch64

# appropriate levels for the host machine
cpus: 8
memory: 16GiB
disk: 300GiB

...

# share a temp space to make sharing files with the host easier
mounts:
- location: "~"
- location: "/tmp/lima"
writable: true

ssh:
localPort: 60023
forwardAgent: true
```

Logs look like this:

```
lars@juniper lima/_output (master) » limactl start alt
INFO[0000] Using the existing instance "alt"
INFO[0000] [hostagent] Starting VZ (hint: to watch the boot progress, see "/Users/lars/.lima/alt/serial.log")
INFO[0001] SSH Local Port: 60023
INFO[0001] [hostagent] new connection from to
INFO[0001] [hostagent] [VZ] - vm state change: running
INFO[0001] [hostagent] Waiting for the essential requirement 1 of 3: "ssh"
INFO[0004] [hostagent] 2023/01/11 21:51:42 tcpproxy: for incoming conn 127.0.0.1:52962, error dialing "192.168.5.15:22": connect tcp 192.168.5.15:22: no route
INFO[0014] [hostagent] Waiting for the essential requirement 1 of 3: "ssh"
INFO[0017] [hostagent] 2023/01/11 21:51:56 tcpproxy: for incoming conn 127.0.0.1:52971, error dialing "192.168.5.15:22": connect tcp 192.168.5.15:22: no route
INFO[0027] [hostagent] Waiting for the essential requirement 1 of 3: "ssh"
INFO[0030] [hostagent] 2023/01/11 21:52:09 tcpproxy: for incoming conn 127.0.0.1:52974, error dialing "192.168.5.15:22": connect tcp 192.168.5.15:22: no route
INFO[0040] [hostagent] Waiting for the essential requirement 1 of 3: "ssh"
INFO[0043] [hostagent] 2023/01/11 21:52:22 tcpproxy: for incoming conn 127.0.0.1:52975, error dialing "192.168.5.15:22": connect tcp 192.168.5.15:22: no route
INFO[0053] [hostagent] Waiting for the essential requirement 1 of 3: "ssh"
INFO[0056] [hostagent] 2023/01/11 21:52:35 tcpproxy: for incoming conn 127.0.0.1:52976, error dialing "192.168.5.15:22": connect tcp 192.168.5.15:22: no route
INFO[0066] [hostagent] Waiting for the essential requirement 1 of 3: "ssh"
INFO[0069] [hostagent] 2023/01/11 21:52:48 tcpproxy: for incoming conn 127.0.0.1:52977, error dialing "192.168.5.15:22": connect tcp 192.168.5.15:22: no route
INFO[0079] [hostagent] Waiting for the essential requirement 1 of 3: "ssh"
INFO[0082] [hostagent] 2023/01/11 21:53:01 tcpproxy: for incoming conn 127.0.0.1:52979, error dialing "192.168.5.15:22": connect tcp 192.168.5.15:22: no route
```

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.