[macOS m1] VM's always in `Unknown` state and timing out on `launch`

canonical / multipass

Multipass orchestrates virtual Ubuntu instances

https://multipass.run

GNU General Public License v3.0

7.86k stars 650 forks source link

[macOS m1] VM's always in `Unknown` state and timing out on `launch` #2623

Open arani-sen opened 2 years ago

arani-sen commented 2 years ago

Describe the bug Each time I try launching a vm, the vm goes into an Unknown state.

To Reproduce How, and what happened?

multipass launch --name test-vm
launch failed: The following errors occurred:
test-vm: timed out waiting for response

Expected behavior What did you expect to happen?

Logs

Additional info

OS: macOS v12.4

multipass   1.9.2+mac
multipassd  1.9.2+mac

Name:           test-vm
State:          Unknown
IPv4:           --
Release:        --
Image hash:     95a027336e19 (Ubuntu 20.04 LTS)
Load:           --
Disk usage:     --
Memory usage:   --
Mounts:         --

Additional context When I initially installed everything was working fine. Closed my laptop and tried again later and everything just stopped working. I have uninstalled both via the script and brew based on the docs, then I installed again and the issue persists.

luis4a0 commented 2 years ago

Hi @arani-sen, it seems SSH is blocked in some way. Did you update recently MacOS?

arani-sen commented 2 years ago

I think so, I have automatic updates so it is safe to assume I did.

luis4a0 commented 2 years ago

MacOS update introduces changes in the firewall. There are some quick fixes for this here. Let me know if that works. Thanks!

avltree9798 commented 1 year ago

Hi @luis4a0 , still got this exact same error, even after the quick fix. I'm on macOS Sonoma

luis4a0 commented 1 year ago

Hi @avltree9798, thanks for the heads up! We didn't try Sonoma yet and we are not sure if it is introducing changes in the firewall. We'll investigate it soon but, as usual, we don't have access to the internals so we can't make more promises than that.

luis4a0 commented 1 year ago

@avltree9798 that said, the root of the issue could be other than Sonoma. So let's try to understand what is happening. Did this issue exist before moving to Sonoma, or you just tried Multipass after installing Sonoma? Can you better describe the issue or should I assume the logs and description of the issue are exact like the original one? Thanks!

dubeypranav4 commented 4 months ago

disabling the firewall helps. I think the multipassd is getting blocked Waiting for ssh. Sonoma has definitely messed with the firewall settings.