macos-13 job crashes without logs

[AkihiroSuda]

Description

macos-13 job crashes after (roughly) 30 minutes, without logs

Platforms affected

• Azure DevOps
• GitHub Actions - Standard Runners
• GitHub Actions - Larger Runners

Runner images affected

• Ubuntu 20.04
• Ubuntu 22.04
• macOS 11
• macOS 12
• Windows Server 2019
• Windows Server 2022

Image version and build link

Image: macos-13
Version: 20230419.1

https://github.com/lima-vm/lima/actions/runs/4799814791/jobs/8596609974?pr=1511

Is it regression?

Yes (macos-12 → macos-13)

Expected behavior

Should not crash without logs

Actual behavior

Crashes after (roughly) 30 minutes without logs

Repro steps

Run a job with macos-13 runner

[ilia-shipitsin]

interesting. I'll have a look

[ilia-shipitsin]

@AkihiroSuda , I tried to run in my fork

seems, it awaits for

time="2023-04-28T12:37:24Z" level=info msg="[hostagent] 2023/04/28 12:37:24 tcpproxy: for incoming conn 127.0.0.1:49278, error dialing \"192.168.5.15:22\": connect tcp 192.168.5.15:22: no route to host"
time="2023-04-28T12:37:34Z" level=info msg="[hostagent] Waiting for the essential requirement 1 of 3: \"ssh\""
time="2023-04-28T12:37:37Z" level=info msg="[hostagent] 2023/04/28 12:37:37 tcpproxy: for incoming conn 127.0.0.1:49279, error dialing \"192.168.5.15:22\": connect tcp 192.168.5.15:22: no route to host"
time="2023-04-28T12:37:47Z" level=info msg="[hostagent] Waiting for the essential requirement 1 of 3: \"ssh\""
time="2023-04-28T12:37:51Z" level=info msg="[hostagent] 2023/04/28 12:37:51 tcpproxy: for incoming conn 127.0.0.1:49280, error dialing \"192.168.5.15:22\": connect tcp 192.168.5.15:22: no route to host"

what's that ? how that routing is supposed to appear ? where it tries to connect to ? is it some qemu vm started on runner ?

[AkihiroSuda]

@ilia-shipitsin Thanks for testing.

• How did you get that log? Is that timeout relevant to the 30-min timeout of the GHA job?
• 192.168.5.15 is a virtual IP that is not accessible from the host. This is an equivalent of 10.0.2.15 of QEMU and Virtualbox.
  Lima uses a Unix socket to dial that virtual IP, but it looks like the virtual network stack is somehow not functional.
  I'm not sure whether that virtual network failure is relevant to the 30-min timeout of the GHA job.
• The "vz" mode uses Apple's Virtualization.framework, not QEMU.

[ilia-shipitsin]

I cloned your repo, removed all build definitions except "vz".

30 min, I guess, defined here ...

[AkihiroSuda]

AFAICS that's the timeout of the step, not the job?

[AkihiroSuda]

Removed nick-invision/retry@v2, and the job is still failing without logs
https://github.com/lima-vm/lima/actions/runs/4832217890/jobs/8610695152?pr=1511