-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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-vmware-desktop provider error cannot load such file #10644
Comments
Hi there. Please check the version of Vagrant you have installed. If it is the 32-bit version, please re-install using the 64-bit version. |
Hi @chrisroberts, I'm sure it is the 64-bit version.
|
Same problem here.
|
Same Issue - cannot load such file -- vagrant/vmware/desktop |
Same issue here - Arch Linux current, using the vagrant 2.2.4 downloaded from the Hashicorp website. VMware Workstation 15.1.0 build-13591040 Updated to add: vagrant 2.2.5 downloaded from the hashicorp site reproduces the problem. |
I have the same problem (on Arch Linux), which makes working with vmware boxes using vagrant impossible.
This is on a fresh install of the OS, but I have tried to remove and reinstall the plugin (plus using the license) as well, to no avail. Note: This all seems to work on an older install (of vagrant and the plugin) on a macOS based machine:
Therefore I have also tried installing version It would be great, if this would be fixed soon, as vagrant becomes pretty useless in my work context otherwise. |
Any updates on this? Fresh install of Manjaro (Arch) seeing this same thing (again): cannot load such file -- vagrant/vmware/desktop vmware --version
VMware Workstation 15.5.0 build-14665864 vagrant --version
Vagrant 2.2.6 vagrant plugin list
vagrant-vmware-desktop (2.0.3, global) Similar issue from almost a year ago as reference: #10472 |
Affecting me as well. |
Vagrant 2.2.7 VMware Fusion 11.5 vagrant-vmware-desktop 2.0.3 plugin on MacOS 10.14. The plugins failed to load properly. The error message given is cannot load such file -- vagrant/vmware/desktop Vagrant 2.2.6 VMware Fusion 11.1 vagrant-vmware-desktop 2.0.3 plugin on MacOS 10.14 worked fine... more or less... |
Same problem with Windows 10 Enterprise edition 64
I don't understand why the version shows as 0.0.1
|
Solved the above issue by running
|
Downgraded to Vagrant 2.2.6 with Fusion at 11.5 vagrant-vmware-desktop 2.0.3 on MacOS 10.15.2 and issue was resolved. Seems to be something introduced on Vagrant 2.2.7 plugin worked fine once downgraded. |
Still receiving the same error on Arch Linux.
|
Vagrant Update: thanks @zoetsekas , your solution helped |
Vagrant 2.2.7, Fusion 11.5.3, vmware-plugin 2.0.3 and macOS 11.15.4, same issue. The above configuration was working fine until I accidentally run a script that called |
VMware Workstation 15 Pro v15.5.6 build-16341506 INFO global: VAGRANT_INSTALLER_VERSION="2"
Information about the Vagrant VMware Utility, including installation https://www.vagrantup.com/docs/vmware/vagrant-vmware-utility.html Path: C:/ProgramData/hashicorp/vagrant-vmware-desktop/certificates/vagrant-ut service key file. This error can occur if the Vagrant VMware Utility Information about the Vagrant VMware Utility, including installation https://www.vagrantup.com/docs/vmware/vagrant-vmware-utility.html Path: C:/ProgramData/hashicorp/vagrant-vmware-desktop/certificates/vagrant-ut Information about the Vagrant VMware Utility, including installation https://www.vagrantup.com/docs/vmware/vagrant-vmware-utility.html Path: C:/ProgramData/hashicorp/vagrant-vmware-desktop/certificates/vagrant-ut Information about the Vagrant VMware Utility, including installation https://www.vagrantup.com/docs/vmware/vagrant-vmware-utility.html Path: C:/ProgramData/hashicorp/vagrant-vmware-desktop/certificates/vagrant-ut |
What is status with this? Cos of above, during last year I was forced to use appimage release and it that time it worked fine until recently Archlinux bumped curl and related pkgs has been rebuilt against one so now I am stuch with #9908. Our company pays licenses for vmware plugin and it is literally unusable. In addition I have to remove vmware plugin to be able to work at least on vbox. I do not understand your motivation behind this, ether fix this plugin or don't sell it. There are multiple issues with vmware providers and noone is giving a shit about it. This is completely unacceptable anymore!! |
This issue is still outstanding for nearly a year, having just paid for a license for a plugin that is totally faulty this seems pretty ridiculous. How long does it take to fix this issue given customers are paying for a working solution? |
I was able to successfully run against VMware Workstation on Linux using the following steps. References:
|
I'm getting the same error on Vagrant 2.2.18 |
Still get this error. Vagrant 2.3.0, vagrant-vmware-desktop (3.0.1, global) |
still error persists on m1 mac Information about the Vagrant VMware Utility, including installation https://www.vagrantup.com/docs/vmware/vagrant-vmware-utility.html Path: /opt/vagrant-vmware-desktop/certificates/vagrant-utility.client.crt |
The "cannot load such file" error on Windows, usually happens when the Command Prompt or PowerShell is using a codepage which is not supported by Ruby. You just need to run this before your command, to change the codepage to UTF-8:
|
@pawaanv to get it working on m1, I installed the utility via home-brew reference: https://gist.github.com/sbailliez/f22db6434ac84eccb6d3c8833c85ad92 |
This has worked for me: |
This also worked for me. lsb_release -a vagrant --version |
cd ~/Downloads/
wget https://releases.hashicorp.com/vagrant-vmware-utility/1.0.21/vagrant-vmware-utility_1.0.21_linux_amd64.zip
sudo mkdir -p /opt/vagrant-vmware-desktop/bin
sudo unzip -d /opt/vagrant-vmware-desktop/bin vagrant-vmware-utility_1.0.21_linux_amd64.zip
sudo /opt/vagrant-vmware-desktop/bin/vagrant-vmware-utility certificate generate
sudo /opt/vagrant-vmware-desktop/bin/vagrant-vmware-utility service install
sudo mkdir -p /opt/vagrant-vmware-desktop/bin
sudo unzip -d /opt/vagrant-vmware-desktop/bin vagrant-vmware-utility_1.0.21_linux_amd64.zip
sudo /opt/vagrant-vmware-desktop/bin/vagrant-vmware-utility certificate generate
sudo /opt/vagrant-vmware-desktop/bin/vagrant-vmware-utility service install This worked indeed, thanks! |
Vagrant version
Host operating system
Windows 10
Guest operating system
Debian stretch
Vagrantfile
Debug output
https://gist.github.com/jadilet/975d7786c7569af5276dcd86c3441bd0#file-vagrant-debug-log
https://gist.github.com/jadilet/82ecd069aa0fb644ef1823e97ab7ddb1#file-vagrant-debug-box-remove-log
Expected behavior
vagrant global-status --prune
command should not be failed after installation thevagrant-vmware-destktop
plugin.vagrant box remove BOX_NAME --provider vmware_desktop --all --force
command should not be failed after installation thevagrant-vmware-destktop
plugin.Actual behavior
Steps to reproduce
vagrant-vmware-desktop
vagrant global-status --prune
The text was updated successfully, but these errors were encountered: