Recent version of Virtualbox 7.1.0 is not supported by vagrant 2.4.1

[mrdc]

Debug output

https://gist.github.com/mrdc/bbde883832d21763ca9f975adb641e10

Expected behavior

Vagrant should work with the recent Virtualbox version as the backend.

Actual behavior

Vagrant doesn't work with the recent Virtualbox version as the backend.

Reproduction information

Vagrant version

Vagrant 2.4.1 vagrant-vbguest (0.32.0, global) Virtualbox 7.1.0-r164697

Host operating system

macOS 14.6.1

Guest operating system

Ubuntu 14.04 64bit

Steps to reproduce

1. Update Virtualbox to 7.1.0-r164697
2. Try to start a box using vagrant up
3. Vagrant shows an error:

   
   % vagrant up
   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 by this version of Vagrant. Please install one of the supported versions listed below to use Vagrant:

4.0, 4.1, 4.2, 4.3, 5.0, 5.1, 5.2, 6.0, 6.1, 7.0

A Vagrant update may also be available that adds support for the version you specified. Please check www.vagrantup.com/downloads.html to download the latest version.

#### Vagrantfile

```ruby
Vagrant.configure('2') do |config|
        config.vm.box = 'ubuntu/trusty64'
       config.vm.provider :virtualbox do |v, override|
                v.memory = 2048
                v.cpus = 2
        end 
end

[mrdc]

Looks like the issue is caused by Virtualbox itself - checking it right now.

[mrdc]

Not confirmed. Virtualbox works fine. So, it's vagrant issue, not VB.

[ftaiolivista]

waiting for vagrant update, a quick workaround:

Edit /usr/bin/VBox

    VirtualBoxVM|virtualboxvm)
        exec "$INSTALL_DIR/VirtualBoxVM" "$@"
        ;;
    VBoxManage|vboxmanage)
    ########################
        if [[ $@ == "--version" ]]; then
           echo "7.0.0r164728"
        else
           exec "$INSTALL_DIR/VBoxManage" "$@"
        fi
        ;;
    ########################
    VBoxSDL|vboxsdl)
        exec "$INSTALL_DIR/VBoxSDL" "$@"
        ;;

[mmatela]

Anyone has a similar workaround for Windows?

[mrdc]

Edit /usr/bin/VBox

Looks like this file is available on Linux and not on macOS. I've searched for awhile on mac and can't see the equivalent.

[lmptg]

waiting for vagrant update, a quick workaround:

Edit /usr/bin/VBox

    VirtualBoxVM|virtualboxvm)
        exec "$INSTALL_DIR/VirtualBoxVM" "$@"
        ;;
    VBoxManage|vboxmanage)
    ########################
        if [[ $@ == "--version" ]]; then
           echo "7.0.0r164728"
        else
           exec "$INSTALL_DIR/VBoxManage" "$@"
        fi
        ;;
    ########################
    VBoxSDL|vboxsdl)
        exec "$INSTALL_DIR/VBoxSDL" "$@"
        ;;

@ftaiolivista thanks. Just confirming here so others can see that this worked for me on EndeavourOS (Arch-based): VirtualBox version 7.1.0 r164728 / vagrant --version # 2.4.1

[Happycoil]

Edit /usr/bin/VBox

Looks like this file is available on Linux and not on macOS. I've searched for awhile on mac and can't see the equivalent.

A macOS equivalent would be to edit /usr/local/bin/VBoxManage directly to hijack the --version parameter:

#!/bin/bash
if [[ $@ == "--version" ]]; then
   echo "7.0.0r164728"
else
    exec /Applications/VirtualBox.app/Contents/MacOS/VBoxManage "$@"
fi

I'm still having issues in my environment, but I don't think it's related. The error I'm encountering is the following (the vm name is nil for some reason):

/opt/vagrant/embedded/gems/gems/childprocess-4.1.0/lib/childprocess/abstract_process.rb:44:in `initialize': all arguments must be String: ["/usr/local/bin/VBoxManage", "modifyvm", nil, "--macaddress1", "<address>"] (ArgumentError)

Running the Vagrantfile in the OP works fine, though.

Edit: It actually looks like the above error is a bug with vagrant + Virtualbox 7.1. I installed 7.0, and my environment works again.

[mrdc]

A macOS equivalent would be to edit /usr/local/bin/VBoxManage directly to hijack the --version parameter:

Thanks! It fixes the issue on macOS and VB 7.1.0+.

[kisp]

I followed the suggestion to edit /usr/bin/VBox, and it worked perfectly. Thanks for the help!

For reference, here's the diff of my changes for better clarity:

--- /tmp/orig/VBox  2024-09-14 15:40:52.961690431 +0200
+++ /usr/bin/VBox   2024-09-14 15:42:05.941525049 +0200
@@ -142,7 +142,11 @@
         exec "$INSTALL_DIR/VirtualBoxVM" "$@"
         ;;
     VBoxManage|vboxmanage)
-        exec "$INSTALL_DIR/VBoxManage" "$@"
+   if [[ $@ == "--version" ]]; then
+     echo "7.0.0r164728"
+   else
+          exec "$INSTALL_DIR/VBoxManage" "$@"
+   fi
         ;;
     VBoxSDL|vboxsdl)
         exec "$INSTALL_DIR/VBoxSDL" "$@"

[corv89]

Unfortunately this workaround doesn't help with M* MacOS, as arm boxes aren't picked (which VirtualBox 7.1 is meant to address)

[aburston]

This worked for me on windows.

In: /c/Program Files/Vagrant/embedded/gems/gems/vagrant-2.4.1/plugins/providers/virtualbox/driver

Edit meta.rb

$ diff -u meta.rb.orig meta.rb
--- meta.rb.orig        2024-09-16 11:37:37.017440100 +0100
+++ meta.rb     2024-09-16 11:33:51.312254400 +0100
@@ -69,6 +69,7 @@
             "6.0" => Version_6_0,
             "6.1" => Version_6_1,
             "7.0" => Version_7_0,
+            "7.1" => Version_7_0,
           }

           if @@version.start_with?("4.2.14")

[jillesme]

What @aburston suggested works. Although on Mac (if you installed Vagrant with Homebrew) the location is /opt/vagrant/embedded/gems/gems/vagrant-2.4.1/plugins/providers/virtualbox/driver

[alexlyapin]

This worked for me on windows.

In: /c/Program Files/Vagrant/embedded/gems/gems/vagrant-2.4.1/plugins/providers/virtualbox/driver

Edit meta.rb

$ diff -u meta.rb.orig meta.rb
--- meta.rb.orig        2024-09-16 11:37:37.017440100 +0100
+++ meta.rb     2024-09-16 11:33:51.312254400 +0100
@@ -69,6 +69,7 @@
             "6.0" => Version_6_0,
             "6.1" => Version_6_1,
             "7.0" => Version_7_0,
+            "7.1" => Version_7_0,
           }

           if @@version.start_with?("4.2.14")

This worked for me. Win10, vagrant 2.4.1, virtual box 7.1.0

[n0nag0n]

I also landed here. I was on Linux Mint and I got this error:

/usr/bin/vboxmanage: 146: [[: not found
7.1.0r164728

What I did to fix it was at the top, change the shebang from /bin/sh to /bin/bash. Worked like a dream.

[dualznz]

running temp meta.rb fix for windows fixed issue for me, make sure your machines are not in a suspended state or you will have to manually open them in virtualbox then poweroff machine, then the up signal will work correctly

[lerichardv]

Edit /usr/bin/VBox

Looks like this file is available on Linux and not on macOS. I've searched for awhile on mac and can't see the equivalent.

A macOS equivalent would be to edit /usr/local/bin/VBoxManage directly to hijack the --version parameter:

#!/bin/bash
if [[ $@ == "--version" ]]; then
   echo "7.0.0r164728"
else
    exec /Applications/VirtualBox.app/Contents/MacOS/VBoxManage "$@"
fi

I'm still having issues in my environment, but I don't think it's related. The error I'm encountering is the following (the vm name is nil for some reason):

/opt/vagrant/embedded/gems/gems/childprocess-4.1.0/lib/childprocess/abstract_process.rb:44:in `initialize': all arguments must be String: ["/usr/local/bin/VBoxManage", "modifyvm", nil, "--macaddress1", "<address>"] (ArgumentError)

Running the Vagrantfile in the OP works fine, though.

Edit: It actually looks like the above error is a bug with vagrant + Virtualbox 7.1. I installed 7.0, and my environment works again.

That solved my issue with the virtualbox 7.1 version, but now when i run vagrant up it throws me this error:

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

Command: ["startvm", "0eb0284d-a036-4e5c-8e0d-76cb431906b8", "--type", "headless"]

Stderr: VBoxManage: error: The VM session was aborted VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component SessionMachine, interface ISession

What could it be?

[stefanlasiewski]

For the record, I ran into a slew of problems when upgrading directly from VirtualBox 7.0 to 7.1. I had to completely uninstall 7.0 first before installing 7.1.

@lerichardv Try a complete uninstall.

[nevalashka]

For the record, I ran into a slew of problems when upgrading directly from VirtualBox 7.0 to 7.1. I had to completely uninstall 7.0 first before installing 7.1.

@lerichardv Try a complete uninstall.

I have the same issue (1st problem and the second after solving 1st). I tried to uninstall virtual box in different ways like via terminal script in file dmg and via storage. But nothing has changed and still got this second error

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

Command: ["startvm", "93d13001-f252-48f7-a4f5-3c92b7245391", "--type", "headless"]

Stderr: VBoxManage: error: The VM session was aborted VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component SessionMachine, interface ISession

[slonopotamus]

Just rollback to VirtualBox 7.0 until Vagrant adds support for 7.1.

[egel]

@slonopotamus thanks for your message. However I am afraid for the macOS with Silicon Chips, there is no official VirtualBox image that could be currently used. At least I did not find any on virtualbox website, only see the v7.1 supports Apple chips.

Although there is an unofficial beta port in brew, that can be installed with brew install --cask virtualbox@beta (which at the moment of writing points to 7.0.21_BETA4-164815) but I've also checked it and is also not working.

If you know maybe you could help us (or someone else) which exact versions of Vagrant & VirtualBox are actually compatible and working with each other for Silicon Chips? Thanks a lot in advance for any hints.

[slonopotamus]

7.0.8 for Apple chips is still available from https://download.virtualbox.org/virtualbox/7.0.8/VirtualBox-7.0.8_BETA4-156879-macOSArm64.dmg

I have no idea whether it works with Vagrant or not. But current issue talks about "recent" versions, so I assume that not recent versions worked properly.

[apgeorge]

Virtualbox 7.0 seems to have only beta support for Apple silicone and hence is giving errors for me, even if I try it manually without vagrant. And the latest patch of 7.0 has completely removed the M1 support and doesn’t even install. The best solution here would indeed be 7.1 + vagrant.

[brlin-tw]

IMHO Vagrant should provide a mechanism(environment variable/command option) to bypass the version check and use a profile that is version-wise closest to the existing VirtualBox installation.

[pkarjala]

Adding to the list; running Vagrant 2.4.1, upgraded to VirtualBox Version 7.1.0 r164728 (Qt6.5.3). Receive the following error:

% vagrant up
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 by this version of Vagrant. Please install one of
the supported versions listed below to use Vagrant:

4.0, 4.1, 4.2, 4.3, 5.0, 5.1, 5.2, 6.0, 6.1, 7.0

A Vagrant update may also be available that adds support for the version
you specified. Please check www.vagrantup.com/downloads.html to download
the latest version.

This is on macOS 14.6.1 on an Intel x86_64 Mac.

[neradp]

There is a newer version of VirtualBox: 7.1.2 Vagrant's new update releases are so slow

[phillipross]

There is a newer version of VirtualBox: 7.1.2 Vagrant's new update releases are so slow

Vagrant's updates have historically been relatively slow, and there have been several times throughout the years where vagrant support for a newer virtualbox version has lagged for awhile. The proposal above from @brlin-tw makes a lot of sense, where relaxed constraints on version checking could let us potentially use newer versions of virtualbox without explicit updates from vagrant if there are no internal changes actually necessary to provide support for newer versions.

[fazlearefin]

This worked for me on windows.

In: /c/Program Files/Vagrant/embedded/gems/gems/vagrant-2.4.1/plugins/providers/virtualbox/driver

Edit meta.rb

$ diff -u meta.rb.orig meta.rb
--- meta.rb.orig        2024-09-16 11:37:37.017440100 +0100
+++ meta.rb     2024-09-16 11:33:51.312254400 +0100
@@ -69,6 +69,7 @@
             "6.0" => Version_6_0,
             "6.1" => Version_6_1,
             "7.0" => Version_7_0,
+            "7.1" => Version_7_0,
           }

           if @@version.start_with?("4.2.14")

Worked fine for me on Linux (Fedora 40); I needed to edit /opt/vagrant/embedded/gems/gems/vagrant-2.4.1/plugins/providers/virtualbox/driver/meta.rb. I prefer this temporary solution over the other one involving changing the /usr/bin/VBox file.

[dualznz]

ive reverted back to virtualbox 7.0, its alot more snappy than the new 7.1 vagrant seems to be alot more responsive as well.

had same lagyness on mac osx, ubuntu so eh i also found no need to update to latest

[Shuna322]

Truly, even if this problem gets fixed with #13503 I don't believe we going to see it in the public release any time soon similar to #13371

[markasbach]

Just for completeness, there are two mentions of this issue on other places:

1. On the Oracle Base blog, there is an article on how to hotfix this issue with Windows as host operating system. Here's the link: https://oracle-base.com/blog/2024/09/12/oracle-virtualbox-7-1/
2. On the VirtualBox forums, there is this thread (without a resolution) on the issue: https://forums.virtualbox.org/viewtopic.php?t=112326

I'll add a link to this ticket to the forum thread in a minute.

[daniel-2647]

I've got an M3 and unfortunately I'm on the same boat as everyone else above. I've tried everything mentioned in this gh issue, including the fixes from the oracle blog post and the PR https://github.com/hashicorp/vagrant/pull/13503/ to no avail, still same error:

vagrant up --provider=virtualbox
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'rockylinux/9'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'rockylinux/9' version '4.0.0' is up to date...
==> default: Setting the name of the VM: LabVM_default_1727725770019_2924
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Booting VM...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "dbcaa7a9-9112-4314-ab95-064bd05d4a44", "--type", "headless"]

Stderr: VBoxManage: error: The VM session was aborted
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component SessionMachine, interface ISession

Vagrantfile

Vagrant.configure("2") do |config|
  config.vm.box = "rockylinux/9"
end

vagrant --version
Vagrant 2.4.1

latest virtualbox version used:

macOS / Apple Silicon hosts

[cjsio]

This worked for me on windows.

In: /c/Program Files/Vagrant/embedded/gems/gems/vagrant-2.4.1/plugins/providers/virtualbox/driver

Edit meta.rb

$ diff -u meta.rb.orig meta.rb
--- meta.rb.orig        2024-09-16 11:37:37.017440100 +0100
+++ meta.rb     2024-09-16 11:33:51.312254400 +0100
@@ -69,6 +69,7 @@
             "6.0" => Version_6_0,
             "6.1" => Version_6_1,
             "7.0" => Version_7_0,
+            "7.1" => Version_7_0,
           }

           if @@version.start_with?("4.2.14")

This should be pinned (if that were a thing in github tickets). C:\Program Files\Vagrant\embedded\gems\gems\vagrant-2.4.1\plugins\providers\virtualbox\driver\meta.rb is the needed Windows path including Win11.

Diff should be pretty clear, but for anyone learning, the way this works is by mapping a 7.1 key-value-pair in the driver_map and likewise routing it to Version_7_0. This tells Vagrant to not throw a fit in the mean time before Vagrant releases a 7.1-supported update.

Thank you much @aburston!

[aymg01]

Same boat as daniel-2647: https://github.com/hashicorp/vagrant/issues/13501#issuecomment-2384039635

MacOS: Sequoia 15.0 Chip: Apple M1 Pro Vagrant 2.4.1 VBox: 7.1.2r164945

[rymuscle]

Looks like this file is available on Linux and not on macOS. I've searched for awhile on mac and can't see the equivalent.

A macOS equivalent would be to edit /usr/local/bin/VBoxManage directly to hijack the --version parameter:

➜  vagrant vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'laravel/homestead'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'laravel/homestead' version '13.0.0' is up to date...
==> default: Setting the name of the VM: vagrant_default_1727948188722_5653
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Booting VM...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "e67317cb-1d33-4b39-bdb4-72d7435bac46", "--type", "headless"]

Stderr: VBoxManage: error: The VM session was aborted
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component SessionMachine, interface ISession

[alberto-dieguez]

$ vagrant up Bringing machine 'vagrant' up with 'virtualbox' provider... ==> vagrant: Importing base box 'xxxxxxxxxxxxxxxxxx'... ==> vagrant: Matching MAC address for NAT networking... ==> vagrant: Checking if box 'xxxxxxxxxxxxxxxxxx' version '1' is up to date... ==> vagrant: Setting the name of the VM: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ==> vagrant: Clearing any previously set network interfaces... ==> vagrant: Preparing network interfaces based on configuration... vagrant: Adapter 1: nat ==> vagrant: Forwarding ports... vagrant: 22 (guest) => 2222 (host) (adapter 1) ==> vagrant: Running 'pre-boot' VM customizations... ==> vagrant: Booting VM... There was an error while executing VBoxManage, a CLI used by Vagrant for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "19da40a8-5154-4909-a938-5963b1777abf", "--type", "headless"]

Stderr: VBoxManage.exe: error: The virtual machine 'xxxxxxxxxxxxxxxxxxxxxxxxxx' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'D:\VirtualBox VMs\xxxxxxxxxxxxxxxxxxxxxxxxxxxx\Logs\VBoxHardening.log' VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine

[brlin-tw]

@alberto-dieguez

The program output has indicated there's a log file that may provide more detail to the error:

Stderr: VBoxManage.exe: error: The virtual machine 'xxxxxxxxxxxxxxxxxxxxxxxxxx' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'D:\VirtualBox VMs\xxxxxxxxxxxxxxxxxxxxxxxxxxxx\Logs\VBoxHardening.log'

Please attach the log (after any necessary personal data sanitation in order to help troubleshoot your problem.

[alberto-dieguez]

Hi @brlin-tw , this is the log. VBoxHardening.log

Edit: I dont know why, but putting this in vagrantfile, vagrant up works:

  config.vm.provider "virtualbox" do |vb|
    vb.gui = true
  end

[robsheldon]

This worked for me on windows. In: /c/Program Files/Vagrant/embedded/gems/gems/vagrant-2.4.1/plugins/providers/virtualbox/driver Edit meta.rb

$ diff -u meta.rb.orig meta.rb
--- meta.rb.orig        2024-09-16 11:37:37.017440100 +0100
+++ meta.rb     2024-09-16 11:33:51.312254400 +0100
@@ -69,6 +69,7 @@
             "6.0" => Version_6_0,
             "6.1" => Version_6_1,
             "7.0" => Version_7_0,
+            "7.1" => Version_7_0,
           }

           if @@version.start_with?("4.2.14")

Worked fine for me on Linux (Fedora 40); I needed to edit /opt/vagrant/embedded/gems/gems/vagrant-2.4.1/plugins/providers/virtualbox/driver/meta.rb. I prefer this temporary solution over the other one involving changing the /usr/bin/VBox file.

Worked perfectly in stock Debian bookworm, same path. Thank you.

[UltherEgo]

This worked for me on windows.

In: /c/Program Files/Vagrant/embedded/gems/gems/vagrant-2.4.1/plugins/providers/virtualbox/driver

Edit meta.rb

$ diff -u meta.rb.orig meta.rb
--- meta.rb.orig        2024-09-16 11:37:37.017440100 +0100
+++ meta.rb     2024-09-16 11:33:51.312254400 +0100
@@ -69,6 +69,7 @@
             "6.0" => Version_6_0,
             "6.1" => Version_6_1,
             "7.0" => Version_7_0,
+            "7.1" => Version_7_0,
           }

           if @@version.start_with?("4.2.14")

The above workaround works. However, this is not a solution to the problem. openSUSE Tumbleweed /usr/share/vagrant/gems/gems/vagrant-2.3.7/plugins/providers/virtualbox/driver/meta.rb

Vagrant 2.3.7 Oracle VirtualBox Manager v7.1.0_SUSE

Repo provider: openSUSE:Tumbleweed openSUSE:Factory

[alpizano]

I'm sure it was stated above, but if you're on MacOS (I'm on Ventura 13.7, on a 2017 MBP w/ Intel silicon), you can simply download the VirtualBox <= 7.0 such that it will be compatible with the latest version of Vagrant, and you won't have to edit any files on your system

Follow Below Steps to Run Windows VM via VirtualBox/Vagrant on MacOS (Easy way I have found)

1. Download link for older/previously released versions of VirtualBox:

***I used version 7.0 https://www.virtualbox.org/wiki/Download_Old_Builds

2. Obviously have Vagrant installed (I'm using version 2.4.1)

$ vagrant --version
Vagrant 2.4.1

3. Clone this repo from github

https://github.com/StefanScherer/windows-docker-machine

4. Navigate to the newly cloned repo directory in your terminal of your choice and run the below command:

vagrant up --provider virtualbox 2022-box

Boom. It should boot up with no errors. Remember you can download the VM extensions tools for VirtualBox as-well (the link is one the same page as the older/previously released builds as they are linked to their respective build release fyi).

You can use the VirtualBox GUI to operate your new VM. Good luck.

[daniel-2647]

Thank you, the instructions above are really appreciated and do work for those who are not dependent on Virtualbox 7.1.0, however, the issue is that Virtualbox 7.1.0 is not supported by vagrant 2.4.1. Installing a prior version is not a solution, since for mac M(X) users (M1, M2, M3), none of the above steps work (if trying to bring up a Virtualbox VM via Vagrant) and Virtualbox 7.1.0 is the only version that works on the new non intel macs (Virtualbox 7.1.0 works, the problem is Vagrant does no work with it).

[Insua]

need update by vagrant

[hv23]

Also running into this issue, 2022 M2 Macbook Air

VirtualBox 7.1.2 Vagrant 2.4.1

Extremely frustrating!

[ichie-Ozor]

@aburston thank you very much, it worked for me W10 vagrant 2.4.1 VirtualBox 7.1.2 all I did was to add: "7.1" => Version_7_0, to the list of versions in the directory you posted. thanks man

[fluidum]

Due to the challenges in keeping support for various hypervisor versions fully up-to-date, it would be helpful to introduce a configurable variable that includes a "without warranties" option. This would allow users to opt into this setting without needing to modify the code directly.

[shadowlmd]

Dear Vagrant developers, please add an option to ignore installed VirtualBox version.