Vagrant 2.2.6 doesn't work with VirtualBox 6.1.0 #178

PaulNeumann · 2019-12-12T02:30:25Z

VirtualBox 6.1.0 has been released. Unfortunately, Vagrant 2.2.6 doesn't work with this new release. This isn't an issue with this repository, but it may affect people using these boxes. It should be fixed in the next release of Vagrant (see hashicorp/vagrant#11249), but here's how to work around the problem in the meantime.

Credits:

@scoter-oracle blogged about a very similar issue last year.
@briancain has developed a fix for the next Vagrant release (see briancain/vagrant@fb4e698)

The workaround requires 3 changes.

First, in the file /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/plugins/providers/virtualbox/plugin.rb, add a line at the end of the Driver module for VirtualBox 6.1, as follows. (On Windows, the file location is C:\HashiCorp\Vagrant\embedded\gems\2.2.6\gems\vagrant-2.2.6\plugins\providers\virtualbox\plugin.rb.)

module Driver
  autoload :Meta, File.expand_path("../driver/meta", __FILE__)
  autoload :Version_4_0, File.expand_path("../driver/version_4_0", __FILE__)
  autoload :Version_4_1, File.expand_path("../driver/version_4_1", __FILE__)
  autoload :Version_4_2, File.expand_path("../driver/version_4_2", __FILE__)
  autoload :Version_4_3, File.expand_path("../driver/version_4_3", __FILE__)
  autoload :Version_5_0, File.expand_path("../driver/version_5_0", __FILE__)
  autoload :Version_5_1, File.expand_path("../driver/version_5_1", __FILE__)
  autoload :Version_5_2, File.expand_path("../driver/version_5_2", __FILE__)
  autoload :Version_6_0, File.expand_path("../driver/version_6_0", __FILE__)
  autoload :Version_6_1, File.expand_path("../driver/version_6_1", __FILE__)
end

Second, in the file /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/plugins/providers/virtualbox/driver/meta.rb, add a line at the end of the driver_map section for VirtualBox 6.1, as follows. (On Windows, the file location is C:\HashiCorp\Vagrant\embedded\gems\2.2.6\gems\vagrant-2.2.6\plugins\providers\virtualbox\driver\meta.rb.)

driver_map   = {
  "4.0" => Version_4_0,
  "4.1" => Version_4_1,
  "4.2" => Version_4_2,
  "4.3" => Version_4_3,
  "5.0" => Version_5_0,
  "5.1" => Version_5_1,
  "5.2" => Version_5_2,
  "6.0" => Version_6_0,
  "6.1" => Version_6_1,
}

Finally, create a new file called version_6_1.rb in the directory /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/plugins/providers/virtualbox/driver. (On Windows, create this file in the folder C:\HashiCorp\Vagrant\embedded\gems\2.2.6\gems\vagrant-2.2.6\plugins\providers\virtualbox\driver.) In this new file, paste the content from here.

With these 3 changes, Vagrant 2.2.6 will work with VirtualBox 6.1.0. I hope this helps!

The text was updated successfully, but these errors were encountered:

piotr-cz · 2019-12-12T09:17:07Z

Thanks for sharing!

MasterCATZ · 2019-12-13T03:39:59Z

Thank you

RvstFyth · 2019-12-16T10:16:21Z

Nice, thanks for the workaround!
For Arch linux the paths where a bit different though:

/opt/vagrant/embedded/gems/gems/vagrant-2.2.6/plugins/providers/virtualbox/plugin.rb
/opt/vagrant/embedded/gems/gems/vagrant-2.2.6/plugins/providers/virtualbox/driver/meta.rb

jonroberts24 · 2019-12-16T15:37:22Z

Do you know when the next version that will work with VirtualBox will be out? Are we talking weeks / months? thanks

PaulNeumann · 2019-12-16T15:51:41Z

@jonroberts24 Only the Vagrant team can answer that. The only indication I've seen is @briancain's comment on the issue in the Vagrant repository.

Michael-Ziluck · 2019-12-16T15:58:23Z

@PaulNeumann When I perform the steps you mentioned, I get the following error message:

A customization command failed:

["modifyvm", :id, "--clipboard", "bidirectional"]

The following error was experienced:

#<Vagrant::Errors::VBoxManageError: There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["modifyvm", "ce8a3576-201c-11ea-978f-2e728ce88125", "--clipboard", "bidirectional"]

Any ideas how I might get this resolved without disabling the bidirectional clipboard?

PaulNeumann · 2019-12-16T16:13:05Z

@ZiluckMichael I don't know; I'm sorry. I suggest asking in the hashicorp/vagrant repository. The thread for the VirtualBox 6.1.0 issue is at hashicorp/vagrant#11249.

scoter-oracle · 2019-12-16T16:15:01Z

While waiting for a fix from Vagrant you can apply that change manually by using "VBoxManage" CLI:

vboxmanage modifyvm <uuid/name> --clipboard-mode bidirectional

The option "--clipboard" has changed to "--clipboard-mode" on 6.1 VirtualBox release.

armenr · 2019-12-17T09:17:48Z

Wow. The first post of this issue saved my butt.

When can we expect a stable update from the Vagrant team?

scoter-oracle · 2019-12-17T09:24:32Z

@karlbunch consider my update above for the Vagrant release supporting VirtualBox 6.1.0 (related to the clipboard change)

paolodenti · 2019-12-22T20:47:38Z

thank you

Redsandro · 2019-12-23T16:21:28Z

Thank you 👍

Don't forget the newly created file needs to be readable by all (e.g. 644), in case you have a different umask when running sudo.

jimfrenette · 2019-12-27T14:55:00Z

Thanks for this!
In fedora 31, the paths are:
/usr/share/vagrant/gems/gems/vagrant-2.2.6/plugins/providers/virtualbox/plugin.rb
/usr/share/vagrant/gems/gems/vagrant-2.2.6/plugins/providers/virtualbox/driver/meta.rb

riksanyal · 2019-12-31T09:55:07Z

While waiting for a fix from Vagrant you can apply that change manually by using "VBoxManage" CLI:

vboxmanage modifyvm <uuid/name> --clipboard-mode bidirectional

The option "--clipboard" has changed to "--clipboard-mode" on 6.1 VirtualBox release.

I still get the original error even after I run this @scoter-oracle

MalikKhattak · 2020-01-01T22:46:10Z

This is a great solution. Only have to be sudo before making changes. Thank you

pchng · 2020-01-04T02:52:01Z

@PaulNeumann thank you very much for the very detailed instructions, both for Linux and Windows! Super easy to follow and understand +1

omgMerrickD · 2020-01-04T21:17:16Z

Thank you so much for this @PaulNeumann! Cheers!

michelvermeulen · 2020-01-06T12:49:17Z

Thanks so much! Works great :)

mikehomee · 2020-01-09T02:52:57Z

Thank you! Works like a charm!

Lewiscowles1986 · 2020-01-11T09:41:16Z

My solution was to visit https://www.virtualbox.org/wiki/Download_Old_Builds_6_0 get supported versions with the highest patch and not manually patch vendor libraries on my computer.

While I would hope Vagrant will patch soon, so I can upgrade both; removing the at-present unsupported version, in favor of 6.0 (October 2019, it's not exactly old); seemed a responsible route.

CYIMANA-Faisal · 2020-01-12T08:46:27Z

VirtualBox 6.1.0 has been released. Unfortunately, Vagrant 2.2.6 doesn't work with this new release. This isn't an issue with this repository, but it may affect people using these boxes. It should be fixed in the next release of Vagrant (see hashicorp/vagrant#11249), but here's how to work around the problem in the meantime.

Credits:

@scoter-oracle blogged about a very similar issue last year.

@briancain has developed a fix for the next Vagrant release (see briancain/vagrant@fb4e698)

The workaround requires 3 changes.

First, in the file /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/plugins/providers/virtualbox/plugin.rb, add a line at the end of the Driver module for VirtualBox 6.1, as follows. (On Windows, the file location is C:\HashiCorp\Vagrant\embedded\gems\2.2.6\gems\vagrant-2.2.6\plugins\providers\virtualbox\plugin.rb.)
module Driver
  autoload :Meta, File.expand_path("../driver/meta", __FILE__)
  autoload :Version_4_0, File.expand_path("../driver/version_4_0", __FILE__)
  autoload :Version_4_1, File.expand_path("../driver/version_4_1", __FILE__)
  autoload :Version_4_2, File.expand_path("../driver/version_4_2", __FILE__)
  autoload :Version_4_3, File.expand_path("../driver/version_4_3", __FILE__)
  autoload :Version_5_0, File.expand_path("../driver/version_5_0", __FILE__)
  autoload :Version_5_1, File.expand_path("../driver/version_5_1", __FILE__)
  autoload :Version_5_2, File.expand_path("../driver/version_5_2", __FILE__)
  autoload :Version_6_0, File.expand_path("../driver/version_6_0", __FILE__)
  autoload :Version_6_1, File.expand_path("../driver/version_6_1", __FILE__)
end
Second, in the file /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/plugins/providers/virtualbox/driver/meta.rb, add a line at the end of the driver_map section for VirtualBox 6.1, as follows. (On Windows, the file location is C:\HashiCorp\Vagrant\embedded\gems\2.2.6\gems\vagrant-2.2.6\plugins\providers\virtualbox\driver\meta.rb.)
driver_map   = {
  "4.0" => Version_4_0,
  "4.1" => Version_4_1,
  "4.2" => Version_4_2,
  "4.3" => Version_4_3,
  "5.0" => Version_5_0,
  "5.1" => Version_5_1,
  "5.2" => Version_5_2,
  "6.0" => Version_6_0,
  "6.1" => Version_6_1,
}
Finally, create a new file called version_6_1.rb in the directory /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/plugins/providers/virtualbox/driver. (On Windows, create this file in the folder C:\HashiCorp\Vagrant\embedded\gems\2.2.6\gems\vagrant-2.2.6\plugins\providers\virtualbox\driver.) In this new file, paste the content from here.

With these 3 changes, Vagrant 2.2.6 will work with VirtualBox 6.1.0. I hope this helps!

ooooooooooooo yeah. Now you are my hero. Thanks, buddy

ghost · 2020-01-12T10:51:22Z

Thank you, it worked!

netsensei · 2020-01-12T13:52:24Z

Works for me! thanks!

Any Fedora 31 users who might stumble across this:

I'm on Fedora 3.1 which pushes kernel 5.4.x on sudo dnf update. VirtualBox 6.0 won't work under kernel 5.4 because the vboxdrv plugin will complain about incompatible kernel modules. Trying to compile the modules will fail since kernel 5.4 is only supported as of VirtualBox 6.1

So, that leaves you with two options:

Manually apply this to get Vagrant 2.2.6 to support VirtualBox 6.1
Don't use kernel 5.4 and stay on the 5.3 branch until Hashicorp pushes a new release which includes support for Virtualbox 6.1 (see: Support Virtualbox 6.1 hashicorp/vagrant#11249 which is already fixed and ready for shipment)

charlmert · 2020-01-13T14:54:24Z

I knew you guys would create a freaking brilliant fix for this,
Thanks you guys works perfectly.

Artistan · 2020-01-14T20:33:03Z

fix still works, thanks!

SmellyFish · 2020-01-16T17:11:18Z

The fix worked, thanks! For step 3, make sure you read the instructions carefully and put the linked contents into version_6_1.rb. I read a little too fast and left the file blank which produced the following error:

/opt/vagrant/embedded/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/plugins/providers/virtualbox/driver/version_6_1 (LoadError)

skobkin · 2020-01-17T09:55:14Z

Is there an easy way to patch the binary provided here: https://releases.hashicorp.com/vagrant/2.2.6/vagrant_2.2.6_linux_amd64.zip
?

ivanorusso · 2020-01-17T15:22:57Z

Thank you, it worked like a charm

jabenninghoff · 2020-01-18T20:42:36Z

Here is a patch file to implement the workaround above: https://gist.github.com/jabenninghoff/a1680f5a7146370b461bb1c38fa8e14f

rbreaves · 2020-01-23T00:21:01Z

I think you are better off remapping 6.1 to 6.0. I have several plugins that need to initialize as well and I think they fail due to the mapping of 6.1 to 6.1.

macOS: /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/plugins/providers/virtualbox/driver/meta.rb
Windows: C:\HashiCorp\Vagrant\embedded\gems\2.2.6\gems\vagrant-2.2.6\plugins\providers\virtualbox\driver\meta.rb

"6.1" => Version_6_0,

yveshwang · 2020-01-23T09:49:12Z

Thank you!

adeoke · 2020-01-28T13:47:30Z

Vagrant 2.2.7 now released. Appears to resolve my problem with virtualbox 6.1.x not being recognised.

machielg · 2020-01-28T13:51:27Z

Fixed with GH-11250

Vagrant 2.2.7 now released. Appears to resolve my problem with virtualbox 6.1.x not being recognised.

scoter-oracle · 2020-01-28T13:56:09Z

Vagrant 2.2.7 adds support for VirtualBox 6.1 - https://github.com/hashicorp/vagrant/blob/v2.2.7/CHANGELOG.md
Closing the issue.

timka · 2020-02-03T22:08:31Z

2.2.7 doesn't work for me

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'kane_project/windows-10' version '1903' is up to date...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 3389 (guest) => 3389 (host) (adapter 1)
    default: 5985 (guest) => 55985 (host) (adapter 1)
    default: 5986 (guest) => 55986 (host) (adapter 1)
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
A customization command failed:

["modifyvm", :id, "--clipboard", "bidirectional"]

The following error was experienced:

#<Vagrant::Errors::VBoxManageError: There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["modifyvm", "ce2ae2de-d509-46e4-82ac-11df167cf2d5", "--clipboard", "bidirectional"]

Stderr: Oracle VM VirtualBox Command Line Management Interface Version 6.1.2
(C) 2005-2020 Oracle Corporation
All rights reserved.

Usage:
# ...

VBoxManage: error: Unknown option: --clipboard
>

Please fix this customization and try again.

$ vagrant -v
Vagrant 2.2.7

scoter-oracle · 2020-02-03T22:48:49Z

@timka this issue has to be reported to the vagrant-project. I already shared this issue with them but it seems that the same had been ignored.

timka · 2020-02-04T14:30:45Z

@scoter-oracle Ah, wrong issue. Sorry for that

scoter-oracle · 2020-02-04T14:33:45Z

@timka I've talked with Vagrant guys, it seems that the "clipboard" mode is not an option managed by Vagrant but custom-code that you have into your box definition. So, you can evaluate to change the "--clipboard" to "--clipboard-mode" into your code. BTW, I've also talked with VBox engineering and we'll get back the support for also the older syntax. Thanks

dkalaluhi · 2020-02-25T21:45:55Z

Still an issue on fedora 31 with the repo version they have. Workaround does indeed work, but in the end, too many wonky things going on...just ended up going with 2.2.7 and fixed everything

ashish-banjare · 2020-03-01T15:07:57Z

/opt/vagrant/embedded/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/plugins/providers/virtualbox/driver/meta (LoadError)

i am getting this error when run vagrant uo command in ubuntu 18.04

and i also give 644 permission to new created file

mojili · 2020-05-15T06:42:28Z

@PaulNeumann
Thank you. The provided solution was great

HenryPineda · 2020-10-05T01:43:43Z

Thanks for sharing. It worked for me!

blecx · 2021-05-08T09:40:58Z

Hi,

on debian the pathes are:

/usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/providers/virtualbox/driver/meta.rb 
/usr/share/rubygems-integration/all/gems/vagrant-2.2.3/plugins/providers/virtualbox/driver/version_6_1.rb

rest as decribed

vagrant init centos/7
vagrant up --provider virtualbox

I only needed to call vagrant up twice. Who knows why...

works

scoter-oracle closed this as completed Dec 12, 2019

rodrigoprimo mentioned this issue Dec 12, 2019

Support Virtualbox 6.1 hashicorp/vagrant#11249

Closed

scoter-oracle reopened this Dec 17, 2019

Redsandro mentioned this issue Dec 24, 2019

Fixes #11249: Add VirtualBox provider support for version 6.1.x hashicorp/vagrant#11250

Merged

makuk66 mentioned this issue Dec 28, 2019

Add vagrantfile docker-solr/docker-solr#268

Merged

markhann mentioned this issue Dec 31, 2019

Vagrant errors when specifying custom Host-Only attached adapter network hashicorp/vagrant#8878

Open

unfulvio mentioned this issue Jan 2, 2020

Problem provisioning with Vagrant 2.2.6, VirtualBox 6.1.0 on Fedora 31 (unmet dependencies) Varying-Vagrant-Vagrants/VVV#2039

Closed

riksanyal mentioned this issue Jan 3, 2020

Getting clipboard error while using vagrant 2.26 with virtualbox 6.1.0 #188

Closed

scoter-oracle mentioned this issue Jan 13, 2020

Vagrant doesn't work with Virtualbox 6.1 even after changes #190

Closed

supkoder mentioned this issue Jan 23, 2020

VBoxManage: error: Unknown option: --clipboard (peru/ubuntu-18.04-server-amd64) ruzickap/packer-templates#57

Closed

sanreee mentioned this issue Jan 23, 2020

VirtualBox 6.1.2 doesn't work with latest Vagrant clong/DetectionLab#374

Closed

triplingual mentioned this issue Jan 27, 2020

VirtualBox + Mojave Version Issue dnoneill/annotate#5

Closed

scoter-oracle closed this as completed Jan 28, 2020

Vagrant 2.2.6 doesn't work with VirtualBox 6.1.0 #178

Vagrant 2.2.6 doesn't work with VirtualBox 6.1.0 #178

Comments

PaulNeumann commented Dec 12, 2019

piotr-cz commented Dec 12, 2019

MasterCATZ commented Dec 13, 2019

RvstFyth commented Dec 16, 2019

jonroberts24 commented Dec 16, 2019

PaulNeumann commented Dec 16, 2019

Michael-Ziluck commented Dec 16, 2019

PaulNeumann commented Dec 16, 2019

scoter-oracle commented Dec 16, 2019 • edited Loading

armenr commented Dec 17, 2019

scoter-oracle commented Dec 17, 2019

paolodenti commented Dec 22, 2019

Redsandro commented Dec 23, 2019

jimfrenette commented Dec 27, 2019 • edited Loading

riksanyal commented Dec 31, 2019

MalikKhattak commented Jan 1, 2020

pchng commented Jan 4, 2020

omgMerrickD commented Jan 4, 2020

michelvermeulen commented Jan 6, 2020

mikehomee commented Jan 9, 2020

Lewiscowles1986 commented Jan 11, 2020

CYIMANA-Faisal commented Jan 12, 2020

ghost commented Jan 12, 2020

netsensei commented Jan 12, 2020

charlmert commented Jan 13, 2020

Artistan commented Jan 14, 2020

SmellyFish commented Jan 16, 2020

skobkin commented Jan 17, 2020

ivanorusso commented Jan 17, 2020

jabenninghoff commented Jan 18, 2020

rbreaves commented Jan 23, 2020

yveshwang commented Jan 23, 2020

adeoke commented Jan 28, 2020

machielg commented Jan 28, 2020

scoter-oracle commented Jan 28, 2020

timka commented Feb 3, 2020

scoter-oracle commented Feb 3, 2020

timka commented Feb 4, 2020

scoter-oracle commented Feb 4, 2020

dkalaluhi commented Feb 25, 2020

ashish-banjare commented Mar 1, 2020

mojili commented May 15, 2020

HenryPineda commented Oct 5, 2020

blecx commented May 8, 2021 • edited Loading

scoter-oracle commented Dec 16, 2019 •

edited

Loading

jimfrenette commented Dec 27, 2019 •

edited

Loading

blecx commented May 8, 2021 •

edited

Loading