utmapp
Cannot connect VM -> host and host -> VM in MacOS sequoia
Describe the issue
After updating from MacOS Sonoma to Sequoia my VM does not see the host and my host does not see the VM. Pinging via host only network IP, or the bridged network IP does not work. I am, however able to ping other network devices (such as my IPhone).
Configuration
- UTM Version: 4.5.4
- macOS Version: 15.0
- Mac Chip (Intel, M1, ...): M2
I was able to connect to it when I run the VM while using the builtin wifi instead of an external ethernet adapter. After the VM is run, I can use the adapter without connection issues (other than ping to the VM being larger).
I have same problem, I can't ssh to VM, prompts 'No route to host'.
I resolved the problem via open System Settings -> Privacy & Security -> Local Network, open all ssh tool, like iterm2 and Royal TSX
I have same problem, I can't ssh to VM, prompts 'No route to host'.
I resolved the problem via open System Settings -> Privacy & Security -> Local Network, open all ssh tool, like iterm2 and Royal TSX
Enabling iTerm fixed the issue for me as well
For me it works again (without changing any settings) after having upgraded MacOS Sequoia to 15.0.1.
UPDATE: I was able to work around this by switching the VM's Network mode from Bridged to Shared. Once I did that everything "just worked". It's not my preferred network mode but in a pinch it got me out of trouble.
Also, note that this didn't just affect UTM, it is affecting the latest VMware fusion build as well. While it could be an issue on Apple's end, I do wonder if it's got more to do with apps not all following the security model to a tee, and that Sequoia happened to be the point of no return.
It reminds me of past major tech cutovers on macOS and other apps that have nothing to do with UTM! In cases like this it can be tough to know and things are not always as they appear. Thoughts welcomed.
I was having this problem intermittently before Sequoia. Even restarting the network manager (for Fedora 40 in my case) didn't help and I'd have to work around it by rebooting the VM, sometimes even shutting down the VM, restarting UTM, then starting up the VM again. Or even the host OS.
As of Sequoia, this keeps failing to work. I see no notification in Privacy & Security > Local Network either.
So I can't ssh in to my VM, and my VM has no outbound network access either.
My VM config:
- Network Mode: Bridged
- Bridged Interface: Automatic
- Emulated Network Card: virtio-net-pci
In my case, I was able to resolve the issue by ensuring that the VMs were on the same subnet as my laptop (which gets its IP from the router via DHCP). To do this, I changed my router's default DHCP range to match the range of the VMs I had already created. I also used bridge mode in UTM, and everything worked fine with macOS 15.0.1.
If you don't have existing VMs, you can just make sure to create them on the same subnet as your Mac from the start.
Also, note that this didn't just affect UTM, it is affecting the latest VMware fusion build as well. While it could be an issue on Apple's end, I do wonder if it's got more to do with apps not all following the security model to a tee, and that Sequoia happened to be the point of no return.
Having the same issue as @jdandrea, VMWare and UTM both don't work in Bridged mode since I updated to Sequoia. Currently running Sequoia 15.5 (24F74). I bet it has something to do with Privacy and Security > Local Network Access but since there's no way to manually add apps to that list the apps themselves have to prompt, and neither UTM nor VMWare do this. Shared mode works as expected. VM is Windows 11 (Arm)
