Skip to content
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 version Issue #11266

Closed
prasant-ku-rout opened this issue Dec 17, 2019 · 2 comments
Closed

Vagrant version Issue #11266

prasant-ku-rout opened this issue Dec 17, 2019 · 2 comments

Comments

@prasant-ku-rout
Copy link

Hello Team , i have installed Vagrant with below specification , while running "Vagrant up" command getting error as mentioned in section below. could you please help to resolve this

Vagrant 2.2.6

Host operating system - MAC OS 10.13 (This is the operating system that you run locally.

Installed Plugin

vagrant-vmware-desktop (2.0.3, global)

Vagrantfile

Vagrant.configure("2") do |config|
config.vm.box = "ubuntu/trusty64"
config.vm.provider "vmware_desktop" do |vmware|
vmware.gui = false
end
end

Expected behavior

It should spin up Ubuntu VM

Actual behavior

Running the "Vagrant Up" Command getting below Error
Vagrant failed to initialize at a very early stage:

**The "VBoxManage" command or one of its dependencies could not
be found. Please verify VirtualBox is properly installed. You can verify
everything is okay by running "VBoxManage --version" and verifying
that the VirtualBox version is outputted.

If you're on Windows and just installed VirtualBox, you have to
log out and log back in for the new environmental variables to take
effect. If you're on Linux or Mac, verify your PATH contains the folder
that has VBoxManage in it.**

Steps to reproduce

References

Are there any other GitHub issues (open or closed) that should be linked here?
For example:

@briancain
Copy link
Member

Hey there @prasant-ku-rout - This is because the box you selected, ubuntu/trusty64, does not have a vmware_desktop provider. It only supports VirtualBox, so when you try to use that box it attempted to use the virtualbox provider instead. I recommend finding a box that supports the vmware_dekstop provider if you wish to continue using that provider. Thanks!

@ghost
Copy link

ghost commented Jan 28, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Jan 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants