"Vagrant could not detect VirtualBox!"

[ghost]

After I ran 'vagrant up', this was the output:

The provider 'virtualbox' that was requested to back the machine 'default' is reporting that it isn't usable on this system. The reason is shown below:

Vagrant could not detect VirtualBox! Make sure VirtualBox is properly installed. Vagrant uses the VBoxManage binary that ships with VirtualBox, and requires this to be available on the PATH. If VirtualBox is installed, please find the VBoxManage binary and add it to the PATH environmental variable.

Then this was the output after I ran 'vagrant ssh':

The provider 'virtualbox' that was requested to back the machine 'default' is reporting that it isn't usable on this system. The reason is shown below:

Vagrant could not detect VirtualBox! Make sure VirtualBox is properly installed. Vagrant uses the VBoxManage binary that ships with VirtualBox, and requires this to be available on the PATH. If VirtualBox is installed, please find the VBoxManage binary and add it to the PATH environmental variable.

How does one add the 'VBoxManage' binary to the PATH environmental variable?

[ptwobrussell]

To take one step back, can I first just ask if you did install Virtualbox as part of the setup instructions? If so, what version (for reference)?

On May 18, 2014, at 5:05 AM, Joe_Pelecanos notifications@github.com wrote:

After I ran 'vagrant up', this was the output:

The provider 'virtualbox' that was requested to back the machine 'default' is reporting that it isn't usable on this system. The reason is shown below:

Vagrant could not detect VirtualBox! Make sure VirtualBox is properly installed. Vagrant uses the VBoxManage binary that ships with VirtualBox, and requires this to be available on the PATH. If VirtualBox is installed, please find the VBoxManage binary and add it to the PATH environmental variable.

Then this was the output after I ran 'vagrant ssh':

The provider 'virtualbox' that was requested to back the machine 'default' is reporting that it isn't usable on this system. The reason is shown below:

Vagrant could not detect VirtualBox! Make sure VirtualBox is properly installed. Vagrant uses the VBoxManage binary that ships with VirtualBox, and requires this to be available on the PATH. If VirtualBox is installed, please find the VBoxManage binary and add it to the PATH environmental variable.

How does one add the 'VBoxManage' binary to the Path environmental variable?

Thank you

— Reply to this email directly or view it on GitHub.

[ghost]

To take one step back, can I first just ask if you did install Virtualbox as part of the setup instructions? If so, what version (for reference)?

Yes I did and the installed VirtualBox's version is 4.3.12 r93733.

[ptwobrussell]

Joe - Are you running Windows, Linux, or Mac OS X? We should be able to get this squared away for you pretty quickly, though it is a bit odd that your Virtualbox install didn't add it for you automatically. That actually concerns me just a little bit since it leads me to believe that something may have gone awry during the install.

[ghost]

Joe - Are you running Windows, Linux, or Mac OS X?

I'm currently running Windows 7 Ultimate (Service Pack 1) on my rig.

We should be able to get this squared away for you pretty quickly, though it is a bit odd that your Virtualbox install didn't add it for you automatically. That actually concerns me just a little bit since it leads me to believe that something may have gone awry during the install.

Yeah, it's quite odd for me too as I already uninstalled the Vagrant, VirtualBox plus followed the instructions from Appendix A again yet it showed the same outputs similar like those from my OP.

By the way, it's pretty cool that the actual author is guiding me through this troubleshooting. Cheers to you, Mr. Russell!

[Gerarudo]

Hi Joe, Mathew,

I had the same issue (I am running Windows 8.1 on a Dell XPS12 ultrabook) but eventually got it to work. In short, I installed and used an older version of Virtualbox, version 4.3.10, and its extensions from here: https://www.virtualbox.org/wiki/Download_Old_Builds_4_3 , for the reasons explained below.

There are a number of threads online reporting this fault, including a couple involving the founder of Vagrant, Mitchell Hashimoto. The core issue appears to be a difference that has emerged in the PATH environmental variable used between Virtualbox and Vagrant to locate VBOXMANAGE. One is set to VBOX_INSTALL_PATH and the other to VBOX_MSI_INSTALL_PATH, so they are out of synch. The discrepancy arose from a change made by Virtualbox. Reportedly, Vagrant will issue an automatic fix for the discrepancy in their next release, version 1.6.3.

I changed to Virtualbox 4.3.10 to fix the problem, based on one user's suggestion, rather than manually fix the path. Here are a couple of threads related to the issue:

https://github.com/mitchellh/vagrant/issues/3852 https://github.com/mitchellh/vagrant/issues/1622

Mathew - I am looking forward to reading the book and putting the information to use. BTW - It took me about 6 hrs to get the VM/iPython system to work (I am comfortable coding in Python normally). Here is where I went wrong:

• installing github, presented me with a Git GUI app and a Git Bash app. I spent about 30 mins in the GUI app failing to find where I could paste the link to the MSW 2nd Edition respository. Having failed, I reverted to the github manual and learned to use the Git Bash app rather than the GUI to get the job done.
• Upon running Virtualbox, it informed me that I had a 'Fatal Error - no bootable medium found'. Essentially it said that I needed a real or virtual CD bootable drive for Virtualbox to run. This was confusing to me and a little disconcerting because my ultrabook has no CD drive. There are about 8 yrs worth of reports related to this issue online. I spent quite a bit of time working on this before I realized that it was a distraction and not relevant in this instance.
• The last and real obstacle was the 'Vagrant could not detect Virtualbox' issue raised and discussed here.

I was a happy camper when the iPython notebook finally loaded and, as a big fan of this subject area, I am looking forward to getting started and using the system now.

Gerard

[ghost]

I had the same issue (I am running Windows 8.1 on a Dell XPS12 ultrabook) but eventually got it to work. In short, I installed and used an older version of Virtualbox, version 4.3.10, and its extensions from here: https://www.virtualbox.org/wiki/Download_Old_Builds_4_3

This also works for me; now I completed the Appendix A.

Kudos to you Gerard! Plus, thanks also to Matthew for replying to my OP!

[rhymn]

Hi,

I had the same problem with Vagrant 1.6.5 and VirtualBox 4.3.16 running on Mac OS X 10.9.4. Fixed by adding: export PATH="/Applications/VirtualBox.app/Contents/MacOS:$PATH"

to .profile in my home folder

so when you run export it should look something like: declare -x PATH="/Applications/VirtualBox.app/Contents/MacOS:/usr/bin:/bin:/usr/sbin......

thanks, david