Vagrant encountered an unexpected communications error with the Vagrant VMware Utility driver. Please try to run the command again

[Deepthi056]

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.

[asidikfauzi]

did you find any solution for this? i am also experiencing the same thing.

[Stromweld]

I experience this occasionally and have to restart the service for it to work again.

[VAVASIN]

Any news on this issue?

[eXsoR65]

I experience this occasionally and have to restart the service for it to work again.

Can you share how that done?

[Karabuzau]

I experience this occasionally and have to restart the service for it to work again.

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}

[w1593950]

I tried all the possible ways, like removing vagrant applications, all the gems and ruby binaries still the same issue :(

❯ sudo vagrant status Password: Vagrant encountered an unexpected communications 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

❯ sudo vagrant up Vagrant encountered an unexpected communications 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

❯ ls ~/.vagrant.d/gems//vagrant-vmware-{fusion,workstation} zsh: no matches found: /Users/w1593950/.vagrant.d/gems//vagrant-vmware-fusion ❯

Any other thoughts or ideas to resolve this issue?

[electropolis]

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 VMware-Fusion-13.6.0-24238079_universal then those VMware Utilities from https://releases.hashicorp.com/vagrant-vmware-utility/1.0.23/vagrant-vmware-utility_1.0.23_darwin_arm64.dmg and of course vagrant-vmware-desktop (3.0.4, global) plugin for vagrant.

Vagrant.configure("2") do |config| 
  config.vm.box = "generic/debian12" # choose a box type for your requirement
  config.vm.box_check_update = false
  config.vm.provider "vmware_desktop" do |vmware|
  vmware.gui = false
  vmware.allowlist_verified = true
end
end

And I get VAGRANT_DEFAULT_PROVIDER=vmware_desktop

❯ vagrant up
Vagrant encountered an unexpected communications 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

Constantly. I mean seriously? This is how it's gonna work on ARM processors ?

== Update I manage to install it by removing vagrant-vmware-utility that was installed from dmg file that I downloaded here https://developer.hashicorp.com/vagrant/install/vmware And trying to install it using brew . Although the above site doesn't really explain how to install utility using brew.

Instead this

brew tap hashicorp/tap
brew install hashicorp/tap/hashicorp-vagrant

use

brew install vagrant-vmware-utility Then I didn't get this error. BUT (It couldn't be easy of course :) ) Im having another one which is a bullshit btw

❯ vagrant up
Bringing machine 'default' up with 'vmware_desktop' provider...
==> default: Verifying vmnet devices are healthy...
==> default: Preparing network adapters...
==> default: Starting the VMware VM...
An error occurred causing VMware to cancel the current operation. Details
of the error causing the cancelation:

This virtual machine cannot be powered on because it requires the X86 machine architecture, which is incompatible with this Arm machine architecture host. See KB-84273.

The full log can be located at:

/Users/konrad/Documents/dev/vagrant/.vagrant/machines/default/vmware_desktop/809c2cf7-cf0a-4263-aae0-2f739eaabe3d/vmware.log

Wait what? I have VMware Utility & Vagrant for ARM64. launching only specific images from vagrant box on arm64 and VMware provider https://portal.cloud.hashicorp.com/vagrant/discover?architectures=arm64&providers=vmware&query=

[Dynamo2k]

I am encountered an issue while installing dc

PS D:\VM\DetectionLab\Vagrant> vagrant destroy dc Vagrant encountered an unexpected communications 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 PS D:\VM\DetectionLab\Vagrant> vagrant reload dc Vagrant encountered an unexpected communications 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 PS D:\VM\DetectionLab\Vagrant> vagrant up dc Vagrant encountered an unexpected communications 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 PS D:\VM\DetectionLab\Vagrant>

what should i do in order to resolve this issue.

[Stromweld]

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.