I am using Vagrant 2.3.2 with VMware Fusion 13.0.1 on a MacBook Pro with a Quad-Core Intel Core i7 processor on MacOS Ventura 13.2.1. I was running the VM through vagrant, closed the MacBook and pulled out the plug for the terminal. This killed the program. However, when I now enter “vagrant” (with any option) from the command line, nothing happens, and there’s no error message (also “vagrant --debug” gives nothing). The VM is still there, and I can open them with VMware Fusion. What happened? Is the provider broken? How can I debug to see what is going on?
Same here. I started my VM (VirtualBox in my case) using “vagrant up” and then any “vagrant” command does NOTHING.
I have the same issue after updating MacOs to Ventura 13.3.1 (a).
Seems every time there is an update there will be an issue with Virtualbox or Vagrant.
I gave access to Virtualbox in Macos settings > Integrity and Security, after updating.
Removed vagrant with brew uninstall and then downloaded the installer, it now works again.