Support virtualbox 5 0 #5603
Support virtualbox 5 0 #5603
Conversation
… of acceptable versions/drivers, and autoloading the file in the virtualbox plugin file.
| @@ -50,6 +50,7 @@ def initialize(uuid=nil) | |||
| "4.1" => Version_4_1, | |||
| "4.2" => Version_4_2, | |||
| "4.3" => Version_4_3 | |||
There was a problem hiding this comment.
Looks like we are missing a comma here
…keep future diffs from highlighting the existing line.
|
So can't wait for this to go into next build. I think many people are using VB5 beta for the new features. |
|
#5560 can be closed if this gets merged |
|
What is the hold up on getting this merged in? |
|
|
|
@sethvargo @michaeldhopkins Sorry, I'm impatient :D #5647 |
|
I agree Stanzilla. I was hoping to already have a new version of vagrant installed and using the new VB beta already. |
|
Vagrant doesn't work in Windows 10 at the moment. The issue is to do with host-only networking component in VirtualBox. I've read that the VirtualBox 5.0 Beta 4 doesn't have this issue but Vagrant won't work with it. So until you get this merged and out there its causing problems for early adopters. I know we bring it upon ourselves please get this one out the door! :) |
|
My pull request #5647 is just waiting for @sethvargo 's approval. |
|
Merged #5647 |
ghost
locked and limited conversation to collaborators
This is in reference to #5572. Using the 4.3 driver for 5.0 works, so adding it is an easy way to extend support to the new version of Virtualbox.