You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Vagrant 2.2.19 (installed via homebrew)
vagrant-vmware-utility 1.0.21 (installed via homebrew)
VMware Fusion 12.2.1 (installed via homebrew)
vagrant-vmware-desktop 3.0.1, global
Host operating system
Big Sur (11.6.2)
Guest operating system
n/a
Vagrantfile
n/a
Debug output
n/a
Expected behavior
When no VM is running vagrant should not listen on any ports.
Actual behavior
vagrant global-status:
id name provider state directory
-------------------------------------------------------------------------------------------------------
d6b997c lin-vm vmware_desktop not running /Users/fasmat/workspace/testvm
The above shows information about all known Vagrant environments
on this machine. This data is cached and may not be completely
up-to-date (use "vagrant global-status --prune" to prune invalid
entries). To interact with any of the machines, you can go to that
directory and run Vagrant, or you can use the ID directly with
Vagrant commands from any directory. For example:
"vagrant destroy 1a2b3c4d"
Vagrant version
Vagrant 2.2.19 (installed via homebrew)
vagrant-vmware-utility 1.0.21 (installed via homebrew)
VMware Fusion 12.2.1 (installed via homebrew)
vagrant-vmware-desktop 3.0.1, global
Host operating system
Big Sur (11.6.2)
Guest operating system
n/a
Vagrantfile
n/a
Debug output
n/a
Expected behavior
When no VM is running vagrant should not listen on any ports.
Actual behavior
vagrant global-status
:sudo lsof -i -P | grep LISTEN | grep vagrant
:Steps to reproduce
vagrant-vmware-utility
The text was updated successfully, but these errors were encountered: