How to troubleshoot connection reset issue

[toolkit]

Hi. I've just installed the arm64 version of rancher desktop onto my Mac.
When I launch rancher desktop, it attempts to start the virtual machine, but I am seeing 'connection reset by peer' error messages in ha.stderr.log:

{"level":"debug","msg":"stdout=\"\", stderr=\"kex_exchange_identification: read: Connection reset by peer\\r\\nConnection reset by 127.0.0.1 port 57899\\r\\n\", err=failed to execute script \"ssh\": stdout=\"\", stderr=\"kex_exchange_identification: read: Connection reset by peer\\r\\nConnection reset by 127.0.0.1 port 57899\\r\\n\": exit status 255","time":"2023-12-06T16:22:23Z"}

A dialog pops up with:
Error: /Applications/Rancher Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl.ventura exited with code 1

Last command run was:
/Applications/Rancher Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl.ventura start --tty=false /Users/myusername/Library/Application Support/rancher-desktop/lima/_config/0.yaml

And the recent logs were:

'time="2023-12-06T16:15:24Z" level=info msg="[hostagent] Waiting for the essential requirement 1 of 5: \\"ssh\\""\n' +
    'time="2023-12-06T16:16:50Z" level=info msg="[hostagent] Waiting for the essential requirement 1 of 5: \\"ssh\\""\n' +
    'time="2023-12-06T16:18:16Z" level=info msg="[hostagent] Waiting for the essential requirement 1 of 5: \\"ssh\\""\n' +
    'time="2023-12-06T16:19:41Z" level=info msg="[hostagent] Waiting for the essential requirement 1 of 5: \\"ssh\\""\n' +
    'time="2023-12-06T16:21:07Z" level=info msg="[hostagent] Waiting for the essential requirement 1 of 5: \\"ssh\\""\n' +
    'time="2023-12-06T16:22:23Z" level=fatal msg="did not receive an event with the \\"running\\" status"\n',
  code: 1,
  [Symbol(child-process.command)]: '/Applications/Rancher Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl.ventura start --tty=false /Users/myusername/Library/Application Support/rancher-desktop/lima/_config/0.yaml'
}

Is there any further debugging I can use to determine why I might be seeing this error?

[toolkit]

For your information. This was happening on Apple M3 chip. Switching from QEMU to VZ emulation appears to solve it.