-
Notifications
You must be signed in to change notification settings - Fork 40
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
Vagrant encountered an unexpected communications error with the Vagrant VMware Utility driver. Please try to run the command again #117
Comments
did you find any solution for this? i am also experiencing the same thing. |
I experience this occasionally and have to restart the service for it to work again. |
Any news on this issue? |
Can you share how that done? |
Я ахуел пока искал решение, короче надо сделать vagrant destroy Check if they exist and verify that they're the correct paths as shown below.$ ls ~/.vagrant.d/gems/*/vagrant-vmware-{fusion,workstation} Remove them$ rm -rf ~/.vagrant.d/gems/*/vagrant-vmware-{fusion,workstation} |
I tried all the possible ways, like removing vagrant applications, all the gems and ruby binaries still the same issue :( ❯ sudo vagrant status https://github.com/hashicorp/vagrant-vmware-desktop/issues ❯ sudo vagrant up https://github.com/hashicorp/vagrant-vmware-desktop/issues ❯ ls ~/.vagrant.d/gems//vagrant-vmware-{fusion,workstation} Any other thoughts or ideas to resolve this issue? |
The same error here. I mean I'm struggle with vagrant on M1 Max for 2 days now. I manage to run qemu only but that damn provider doesn't allow me create multiple network interfaces. So I decided to go with VMware fusion. Installed
And I get
Constantly. I mean seriously? This is how it's gonna work on ARM processors ? == Update Instead this
use
Wait what? I have VMware Utility & Vagrant for ARM64. |
I am encountered an issue while installing dc PS D:\VM\DetectionLab\Vagrant> vagrant destroy dc https://github.com/hashicorp/vagrant-vmware-desktop/issues https://github.com/hashicorp/vagrant-vmware-desktop/issues https://github.com/hashicorp/vagrant-vmware-desktop/issues what should i do in order to resolve this issue. |
essentially this is a bad error message and something is causing the service to stop. Start it back up and it should work again. Long term fix for the service would be nice though. |
same issue is going with me unable to sort it out can anyone help |
Vagrant version
Vagrant 2.4.1
Vagrant VMware plugin version
vagrant-hostmanager (1.8.10, global)
vagrant-vbguest (0.32.0, global)
vagrant-vmware-desktop (3.0.3, global)
Vagrant VMware utility version
1.0.21
Host operating system
MACOS M1.
Guest operating system
Ubuntu,Fedora.
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.19"
config.vm.provider "vmware_desktop" do |vmware|
vmware.ssh_info_public = true
vmware.gui = true
end
end
Debug output
Provide a link to a GitHub Gist containing the complete debug output:
https://www.vagrantup.com/docs/other/debugging.html. The debug output should
be very long. Do NOT paste the debug output in the issue, just paste the
link to the Gist.
Expected behavior
What should have happened?
It should bring up the VM form the Vagrantfile.
What actually happened?
Steps to reproduce
1.Open the directory which has Vagrantfile for the VM.
2.vagrant up
3.Error occurs.
when trying to bring up virtual machines using vagrant up command I'm getting above error. If I manually download and install VMWare utility from the net , The command works and brings up VM. But next day again same error occurs.
The text was updated successfully, but these errors were encountered: