-
Notifications
You must be signed in to change notification settings - Fork 11
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
loaded daisy and vagrant up failed because virtualbox was at the latest version #16
Comments
What version of Vagrant are you using? Also, what host operating system are you on? |
Thanks for the heads-up, @adrianjbriscoe! Sounds like this could be a known issue between Vagrant and VirtualBox - dealt with something like it recently, too: hashicorp/vagrant#5572 There are other host OS dependent factors, in particular with Windows 10 at this time, hence @kdavisk6's questions. |
hi kdavis6 |
Thanks, @adrianjbriscoe - have you tried updating Vagrant to 1.7.3 or later? Per the thread I mentioned earlier on the vagrant dev github, it sounds like Vagrant support for VirtualBox 5.x was only very recently added (in the past 3 weeks). |
thank you, everyone issue not a daisy one - sorry for this post ( a little new to this virtual world) upgraded vagrant to Vagrant 1.7.4 and virtual-box 5 with latest extensions no problem thank you again Matt spot on resolved |
No worries, @adrianjbriscoe! Glad you got it working, and, if anything, having this discussion here might help others who run into the same thing. Thanks for posting, and for checking out daisy! |
No thank you for giving us these great tools to try or use in earnest - On Monday, August 3, 2015, Matt Wagner notifications@github.com wrote:
|
loaded daisy and vagrant up failed because virtualbox was at the latest version 5 with latest extensions
Vagrant has detected that you have a version of VirtualBox installed
that is not supported. Please install one of the supported versions
listed below to use Vagrant:
4.0, 4.1, 4.2, 4.3
The text was updated successfully, but these errors were encountered: