-
Notifications
You must be signed in to change notification settings - Fork 660
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Instances fail to start after making network changes on macOS host #2222
Comments
Hi @TwoLeggedCat, make sure you have Internet Sharing disabled in Settings/Sharing. |
Thanks for the hasty reply; I do. |
@TwoLeggedCat you mean you do have it disabled? This error pops up when macOS prevents the VM from creating its network. You may try enabling Internet Sharing and disabling it again, that could clear some internal macOS state. Rebooting could also help. Let us know please! |
@Saviq yes, I have Internet Sharing disabled, and haven’t had it enabled in about a year to my memory. I’ll try rebooting and then disconnecting again when I get back to my computer. |
@Saviq I went through the following steps:
At this point, multipassd.log
Edit: woops, accidentally closed this. |
Thanks @TwoLeggedCat, so it's this that makes it go bad:
Hyperkit tries to set up networking, but macOS is in a state preventing that. If you then reboot without the iPhone plugged in, does it work ok? What about if you enable and disable Internet Sharing? |
@Saviq enabling and disabling Internet Sharing changed nothing; rebooting with the iPhone unplugged allowed me to launch it. After plugging the iPhone back in, I could still launch the instance. It seems it only starts to break when I unplug the iPhone, not when I plug it in. |
Thanks @TwoLeggedCat, unfortunately it's an unsolved issue in xhyve/hyperkit, there's a number of unanswered issues out there (machine-drivers/docker-machine-driver-xhyve#85, machine-drivers/docker-machine-driver-xhyve#107). That said, we're moving to QEMU as our preferred VM backend on macOS, it would be interesting if the issue is seen there as well. If you're willing, please try this installer: And use |
@Saviq, with
Using that build with qemu did seem to fix all the problems with Also, to confirm:
|
Yeah so that's the same problem - macOS doesn't allow to use the virtual network subsystem for some reason. Thanks for diving in, we'll need to look for potential solutions to this. |
Just a note, I managed to recreate this problem with multipass 1.8.0 by ctrl-c'ing (aggressively) during a launch when I didn't want to continue launching that machine (wrong default image/alias). This was on an M1 Macbook Pro running Monterey 12.3.1. Thought this might give you a starting point for a reproducible case for diagnosing and debugging the issue!
|
My internet connection currently comes from an iPhone hotspot over a lightning cable.
After removing all instances, I can create a new one with
I then stopped the instance with
sudo shutdown now
, unplugged the iPhone, and tried to launch it again withm shell pet-gadwall
:The last few lines of
/Library/Logs/Multipass/multipassd.log
:Stopping the daemon with
sudo kill pid
and attempting to launch the instance the same way succeeds as normal.The daemon is running as root.
macOS Catalina version 10.15.7 (19H1323)
I installed Multipass using the pkg file from GitHub releases, not Homebrew (nor do I have Homebrew on this machine).
Also worth noting is that, when I use
m list
after receiving the startup error, the instance's state is shown as "Starting." Stopping the instance appears to run as normal but has no effect; I can still not start it again after doing so and the state is still shown as "Starting." I can also start a new instance after making the network change, I just cannot start one that was running with internet after disconnecting from the internet (until I restart the daemon).The text was updated successfully, but these errors were encountered: