Skip to content
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

Support Virtualbox 5.1 #7411

Closed
zippy1981 opened this issue Jun 9, 2016 · 15 comments
Closed

Support Virtualbox 5.1 #7411

zippy1981 opened this issue Jun 9, 2016 · 15 comments

Comments

@zippy1981
Copy link

@zippy1981 zippy1981 commented Jun 9, 2016

I'm not on a machine I can send a PR from, but these exact steps with the obvious modifications work.

I looked briefly at the release notes and I don't think there are any new configuration options worth tweaking the driver over.

@sethvargo
Copy link
Contributor

@sethvargo sethvargo commented Jun 9, 2016

Hi there,

Vagrant already supports VirtualBox 5.0. I just looked and there does not seem to be downloads for VirtualBox 5.1 yet: https://www.virtualbox.org/wiki/Downloads

@jfilip
Copy link
Contributor

@jfilip jfilip commented Jun 9, 2016

@sethvargo FWIW you can download the current beta from this forum post: https://forums.virtualbox.org/viewtopic.php?f=15&t=78053

@zippy1981
Copy link
Author

@zippy1981 zippy1981 commented Jun 10, 2016

@sethvargo there is a beta. there have actually been two 5.1 beta releases. Now would be the time to add support, for detecting the versions. Of course auto downloading would not make sense.

@sethvargo
Copy link
Contributor

@sethvargo sethvargo commented Jun 10, 2016

Hi @zippy1981

It is our general policy that we do not add support for the beta versions until they are officially released. It is very common for the betas to have bugs or broken functionality that is resolved before the final release. Vagrant often gets blamed for these bugs, so it's our policy to not add support until the release is made official. I'll keep this issue open until then. Thank you for understanding!

@gtirloni
Copy link

@gtirloni gtirloni commented Jun 23, 2016

Vagrant 1.8.4 works fine with VirtualBox 5.1 BETA3 (5.1.0_BETA3r108118), after modifying the code manually. Tested bidirectional clipboard, synced folders and port forwarding on a Fedora 24 box.

@Stanzilla
Copy link
Contributor

@Stanzilla Stanzilla commented Jul 12, 2016

@dominikzogg
Copy link

@dominikzogg dominikzogg commented Jul 13, 2016

Add version in:

embedded/gems/gems/vagrant-1.8.4/plugins/providers/virtualbox/driver/meta.rb:64
embedded/gems/gems/vagrant-1.8.4/plugins/providers/virtualbox/plugin.rb:58

Copy file:

embedded/gems/gems/vagrant-1.8.4/plugins/providers/virtualbox/driver/version_5_0.rb =>
embedded/gems/gems/vagrant-1.8.4/plugins/providers/virtualbox/driver/version_5_1.rb

Replace the version in the copied file

@thom-nic
Copy link

@thom-nic thom-nic commented Jul 13, 2016

FYI: Official VBox 5.1 release announcement is on the HN frontpage, this issue is linked in comments so it will probably get a lot more attention soon.

@d-ph
Copy link

@d-ph d-ph commented Jul 13, 2016

When could we expect vagrant 1.8.5 to be released?

@sethvargo
Copy link
Contributor

@sethvargo sethvargo commented Jul 14, 2016

@d-ph look at the milestone 😄

@infabo
Copy link

@infabo infabo commented Jul 14, 2016

Can anyone provide a vagrant build to be used with VB 5.1, please? I'm on Windows Insider Preview (@#$@#$ Microsoft) and 5.0 is broken like hell (5.1 runs well).

@gtirloni
Copy link

@gtirloni gtirloni commented Jul 14, 2016

@infabo you have to either make the changes to Vagrant manually, wait for the 1.8.5 milestone or go back to VirtualBox 5.0.24.

You can also built from source with these instructions.

@infabo
Copy link

@infabo infabo commented Jul 14, 2016

Ok. thanks. VB 5.0.22 is not working for me (Host-only adapter issue).

@d-ph
Copy link

@d-ph d-ph commented Jul 14, 2016

@sethvargo Thanks. So the 1.8.5 is due to be released in September 1, 2016.

It's great that this project's release plan is so organised. Could this be possible to backport #7574 to 1.8.4 and release a patch release 1.8.4.1? This would make so many people around the world a little bit happier :)

Thanks.

@Jalle19
Copy link

@Jalle19 Jalle19 commented Jul 14, 2016

Wait what? I'll have to run a custom build with scary warnings for two months because no one dared to copy-paste a file and change a version number a month ago when the betas started getting attention? Come on! A 1.8.4.1 release would indeed be nice.

@hashicorp hashicorp locked and limited conversation to collaborators Jul 14, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
10 participants