search

Snergster / virl_boxcutter

virl on packet small vm based on the mighty boxcutter box
13 stars 9 forks source link

vagrant virtualbox - latest not supported #3

Open mineumann opened 7 years ago

mineumann commented 7 years ago

It seems that with virtualbox/vagrant plugin you mention the latest virtualbox software is not supported:

The provider 'virtualbox' that was requested to back the machine 'default' is reporting that it isn't usable on this system. The reason is shown below:

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, 5.0

5.0 "runs out" as mentioned on virtualbox.org and shouldn't be used any longer it seems - so what todo?

At least you should mention it in your documentation. Thank you.

thorr18 commented 7 years ago

@mineumann They added 5.1 driver to Vagrant 1.8.7, so that's the version I installed.

Snergster commented 7 years ago

bah..missed the original comment...so is this still an open problem or not?

thorr18 commented 7 years ago

@Snergster , yes. If a Windows user follows the boxcutter directions, they will need to also downgrade to VirtualBox 5.0 to be compatible. 5.0 is End Of Life as of May 2017

Also, though the directions say Windows users must use Vagrant 1.7.4, I would point out that OSX users are now also unable to use the newest Vagrant (1.9.x), as I documented here. As I continued to have issues with 1.8.7, I ended up on 1.8 and so have had to downgrade the VirtualBox just like Windows users. I can't yet say definitively that is the correct version of Vagrant for OSX users to downgrade to, because all VIRL deployments to Packet.net are failing for everyone.

thorr18 commented 7 years ago

Note, 5.0 is End Of Life after May 2017. It is no longer supported. I think that's what was meant by it "runs out". So, ideally, a newer Vagrant that includes the 5.1 driver would work.