Vagrant not finding VirtualBox 5.0.X on Mac OSX #6431
Labels
Comments
|
which OS X are you running? |
|
Yosemite 10.10.5 |
|
Hi @scarstens Thank you for opening an issue, and I am sorry you are having issues with Vagrant + VirtualBox. I have almost the exact setup locally and Vagrant is working as expected. Are you running a yostemite beta by chance? Are you able to share the output of the vagrant command in debug modehttps://docs.vagrantup.com/v2/other/debugging.html? |
|
Sorry for the delay, I sure can: |
|
Hi @scarstens Could you please uninstall all but the core plugins and try again? As part of our support process, we ask users to uninstall all plugins, since plugins can change Vagrant's behavior. |
|
Done, same issue: |
|
Hi @scarstens Could you please share your Vagrantfile as well? |
|
@sethvargo I did that in the original issue comment, I did a cat of the vagrant file, its very simple and pulled it in from the docker website documentation. |
|
I'd be happy to try any vagrantfile, nothing works I searched around the internet and forums for almost 5 hours before creating this issue here. I have tried quite a wide variety of things to fix this issue. You should be able to recreate this issue on a new or clean virtual osx machine by:
This all came up because I'm trying to use docker-machine and AWS EB instances, but also using vagrant for local development of PHP. My solution, was running docker-machine in virtualbox and vagrant in parallels... but that's not ideal. |
|
Hi @scarstens I have all of those tools installed locally, and it works fine. Additionally, due to Vagrant and Docker's popularity, I would expect many users be facing this issue. The fact that other users aren't reporting this issue (and that I am unable to reproduce the issue), leads me to believe there is something with your environment that is different. That doesn't mean it's not a bug 😄, but the first thing I do on each issue is try to reproduce, and I can't. Can you |
|
Agreed with @sethvargo that we'd be hearing a lot more about this if it was widespread which leads to a system configuration issue. The way Vagrant checks for VirtualBox is to check for |
|
|
|
@scarstens What about the output from: |
|
sure, it was in the original issue entry as well, but here it is as it stands today (still broken) |
|
Hi @scarstens How did you install Vagrant and VirtualBox? I am still unable to reproduce this issue. I wonder if the docker toolbox is installing a modified version of VirtualBox. Could you please download and install VirtualBox from virtualbox.org? |
|
In an effort to reproduce the steps, I'm going to wipe my macbook, install docker toolbelt and setup docker-machine again, then install vagrant again and see if I have the same results. |
|
Hi @scarstens I don't know how docker toolbelt installs virtualbox or at which version. Can you try just installing virtualbox via virtualbox.org? |
|
When you install virtualbox that way, docker-machine doesn't load properly, something about the order of when things are installed and how it gets configured. |
|
Also, I just wanted to say thanks for your support, since I hadn't said that yet. 👍 |
|
@scarstens always happy to help a fellow Seth 😄. Yea, I'm willing to bet it's a version/location thing. |
|
well, it must not just be the docker-toolbox, I wiped the mac, and started from scratch, installed docker first, setup docker-machine, loaded it without a problem, then installed vagrant from brew and it also loaded itself up in virtualbox just fine. guess it was something else, just glad its all working together now. |
|
I didn't have to go as far as wiping my mac, but I did have to uninstall then reinstall Vagrant from its DMG to get it working on a mac that had been upgraded to Yosemite sometime after the initial install of Vagrant. |
|
I had the same issue on Mac OS X El Capitan. Could resolve it with using first 4.3 and then upgrade to 5.0.24 (https://www.virtualbox.org/wiki/Download_Old_Builds_5_0). Hope that helps. |
|
FWIW, this is an issue with the latest VBox on homebrew cask. I recently updated a working VirtualBox installation to the latest, which reproduced this behavior. This also occurred on a fresh system. |
|
I ran into the same issue with Vagrant 1.8.4 and VirtualBox 5.1 (clean system, no brew cask, no docker) Downgrading to Virtualbox 5.0.x solved the issue for me. |
|
I had the same issue as @rrichter and downgrading to Virtualbox 5.0.24 also worked for me. |
|
@rrichter Thank you! You solve my problem! |
|
I also had the same issue as @rrichter and downgrading to Virtualbox 5.0.24 also worked for me. |
|
I had the same issue as rrichter (Vagrant 1.8.4, VirtualBox 5.1 on Ubuntu). The problem is Vagrant 1.8.4 does not support 5.1 yet. You can downgrade to get back to an officially supported stack or you can manually tweak 3 ruby files to get a proper mapping for 5.1, the syntax is described in this github comment: #5572 (comment) |
|
Same issue as @rrichter I uninstalled VirtualBox 5.1, installed VirtualBox 5.0 an it worked 👍 |
|
@NNA, same worked for me too |
|
OSX El Capitan 10.11.5, Vagrant 1.8.4, VirtualBox-5.1.0-108711-OSX.dmg same problem, downgrading to VirtualBox-5.0.26-108824 resolved the problem thanks @rrichter |
|
I'm on OSX 10.10.5, Vagrant 1.8.5, VirtualBox-5.0.26 r108824, and getting the same problem. I can start a brand new vagrant in a new folder, install the guest OS, and it'll run, but after an initial run, Vagrant can never find virtualbox again. I have followed all previous suggestions, including completely uninstalling Vagrant and Virtualbox, deleting the .vagrant.d/ folders, and re-init'ing. |
|
I downgraded to vagrant 1.8.4 and virualbox 5.0.26 and everything is On Tue, Aug 30, 2016 at 8:56 AM, JP Bader notifications@github.com wrote:
Best regards, |
|
I had the same issue on OSX 10.10.5, Vagrant 1.7.2, VirtualBox-5.0.26-108824 Upgrading Vagrant to 1.8.5 has solved this issue. |
|
Still a similar issue with latest version of vagrant: You're running an up-to-date version of Vagrant! |
|
by executing the following command, i got it to work properly: export VAGRANT_DEFAULT_PROVIDER=virtualbox |
|
Same issue here, similar to @ben-tazulev , Vbox 5.0.10 and vagrant 1.7.2. Upgrading vagrant to 1.8.6 fixed it. UPDATE: worked once, back to the same state now... I tried upgrading Vbox to 5.0.26 but still not working... UPDATE 2: renaming .vagrant/machines/VirtualBox to .vagrant/machines/virtualbox seems to work fine... |
|
Thanks @cabezayunke Update 2 worked for me too. |
|
Renaming .vagrant/machines/default/VirtualBox to .vagrant/machines/default/virtualbox did the trick for me. I'm on a case-insensitive HFS+ drive, not sure what is the default. |
|
I had the same issue. Deleting the |
|
Had the same issue. Uninstalling Vagrant and re-installing it did the trick and took like 3 minutes. Uninstall: Reinstall: |
|
Downgrading to Virtualbox 5.0.x solved the issue for me too |
|
Same issue Working with You're running an up-to-date version of Vagrant! renaming .vagrant/machines//VirtualBox to .vagrant/machines//virtualbox worked fine... |
|
Having this problem in openSUSE Tumbleweed. Would prefer to not have to downgrade - -I'd no longer be using the package manager. My |
|
Fixed in latest version of vagrant. I'm on 1.8.1 locally due to packages available in repo. Cloned master, built from source, no trouble |
|
Had the same issue: Richards-MacBook-Pro:cruk01 richardknop$ vagrant --version
Vagrant 1.9.3
Richards-MacBook-Pro:cruk01 richardknop$ VBoxManage --version
5.1.18r114002@cabezayunke The second solution worked for me too. Renaming .vagrant/machines/VirtualBox to .vagrant/machines/virtualbox ... |
|
I tripped over this (VirtualBox 5.1, with vagrant 1.7 on Mac OS 10.11). My troubles went away after I'd installed a newer vagrant (1.9.x) and then spawned a new terminal. |
|
After installing new VirtualBox version 5.1.3 from 5.0.10, Vagrant can't find VirtualBox. Try installing new Vagrant 2.0.0 from 1.8.1, It works. |
|
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
locked and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
and others
I can't find any reason why vagrant won't work with VirtualBox 5, but for some reason it just won't detect that virtualbox is installed. Here is the CLI output of related parts:
The text was updated successfully, but these errors were encountered: