-
Notifications
You must be signed in to change notification settings - Fork 71
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
[Documentation] Does not work with VirtualBox 5.0 #43
Comments
What version of vagrant are you running? See also hashicorp/vagrant#5572 |
vagrant --version |
Huh. According to the Vagrant documentation, it should be working. |
No worries, I downgraded to VirtualBox 4.3 and all is swell. |
It's not working against vbox 5.0 |
I have it working with VirtualBox 5 and vagrant 1.7.4 |
@itxx00 Please provide specific environmental variables, including Operating System version and Vagrant version (vagrant --version) For example, I personally encountered Virtualbox 5 errors on OSX 10.7.5 (Lion) with Vagrant 1.7.4. |
works on mac osx el capitan |
Doesn't work for me with Ubuntu 14.04 LTS with VirtualBox Version: 5.0, Vagrant 1.7.4. I'm seeing the same behaviour as Brad. Just switch from NIXOS cause of random seg-faults... |
Slightly different output, after trying later in the day. Seems to die after installing Java. |
Also tried with VirtualBox 4.3.34 on Ubuntu, (4.3.10 no longer works with new Linux kernels and I couldn't install it), and I can't get it to work either way. |
@nigelgbanks that's no good! Are you getting the same error as before? Or something different? |
Same as before, I've got it to run on the misses Mac book though, so maybe this is just an issue in Linux? |
@nigelgbanks no. Definitely not OS specific given other folks issues above. |
Seems to be more prominent on Linux. Which is sad... since we're targeting linux :( Something about how it virtualizes itself doesn't play well with Karaf. |
FYI, we're hashing this out in #111. We may need you to test, @nigelgbanks. |
No problem I can test. |
VirtualBox 5.0.10_Ubuntu r104061 Everything builds fine. |
I haven't heard any issues on this in a while, so I'm going to close it for now. If we have to re-open it, we can. |
New users who have never installed VirtualBox, will go for the prominently marketed 5.0 version on virtualbox.org. Existing VirtualBox users, may naturally assume the need to upgrade to the latest version (my story).
Requirements on the install/README page should be updated to reflect this pitfall, maybe with a specific recommendation for VirtualBox 4.3.
Error when "vagrant up" is ran against VirtualBox 5.0:
The text was updated successfully, but these errors were encountered: