I just upgraded my mac m2 to Sonoma 14. Now vagrant is stuck on "Waiting for the VM to receive an address...". This is my Vagrantfile:

[phemmyog79]

          I just upgraded my mac m2 to Sonoma 14. Now vagrant is stuck on  "Waiting for the VM to receive an address...". This is my Vagrantfile: 

Vagrant.configure("2") do |config| config.vm.box = "spox/ubuntu-arm" config.vm.box_version = "1.0.0" config.vm.network "private_network", ip: "192.168.56.11" config.vm.provider "vmware_desktop" do |vmware| vmware.gui = true vmware.allowlist_verified = true end end

pls help

Originally posted by @phemmyog79 in https://github.com/hashicorp/vagrant-vmware-desktop/issues/37#issuecomment-1771759598

[phemmyog79]

My config: vmware fusion 12 tech preview + vagrant-vmware-desktop plugin version=3.0.1 + Vagrant 2.3.7

[SloaneTribble]

Same issue, running Vagrant 2.4.1, VMware Fusion 13, vagrant-vmware-desktop (3.0.3, global), Vagrant VMware utility version 1.0.22, Host OS: Mac Sonoma 14.2.1 (23C71), Guest OS: Debian 11 Bullseye

Debug output: https://gist.github.com/SloaneTribble/46ea0b092f1b9dbe4dc73744b0e41ac2

Steps to reproduce:

vagrant init sloanetribble/vmware-fusion13 \
  --box-version 0.1.0
vagrant up

[mikeroySoft]

Is this on arm64 or x86/amd64?

I was able to boot it (sloanetribble/vmware-fusion13) on Apple silicon with Fusion 13.5. Took a while waiting for network, but it eventually got there, tho vagrant ssh was failing. I opened the VM console from Fusion directly and was able to interact with the shell, I could see it uses Linux kernel 5.10.something.

There are known weird issues (not within Fusion) in pre-6.x kernels which we patched (and they were subsequently picked up in 5.19 and later). So probably something related to that.

I also tried bento/debian-12-arm64 and that worked flawlessly.

I'd try rebuilding the box with a newer base OS that has a 6.x or newer kernel if its on a Mac with Apple silicon.

If it's Intel... that's something I'd have to dig into further.

[SloaneTribble]

@mikeroySoft Arm64, sorry for the lack of clarity.

[eszense]

Similar issue here. Would this workaround help?

[Cloudadapt]

I just upgrate to sonoma 14.5 and I downloaded Fusion 13 for personal use, I am getting this error message please I need help:

vagrant up web01 Vagrant encountered an unexpected communication error with the Vagrant VMware Utility driver. Please try to run the command again. If this error persists, please open a new issue at:

https://github.com/hashicorp/vagrant-vmware-desktop/issues

[Stromweld]

You may have to restart the vagrant-VMware-utility service vagrant-VMware-desktop plugin used to talk to VMware-fusion. Or just run 'brew reinstall vagrant-vmware-utility' and that'll start the service after install.