Bug 1829060 - Add VirtualBox 6.1 support to Vagrant
Summary: Add VirtualBox 6.1 support to Vagrant
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: vagrant
Version: 31
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Pavel Valena
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-28 19:38 UTC by Dridi Boukelmoune
Modified: 2020-04-29 00:26 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-29 00:26:39 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Dridi Boukelmoune 2020-04-28 19:38:19 UTC
Description of problem:

I use vagrant with VirtualBox boxes and for some of them I can't have libvirt alternative images. I get VirtualBox from rpmfusion repositories but a while ago it was upgraded to 6.1, which isn't supported by Vagrant 2.2.6.

I understand that rpmfusion third party software is irrelevant, but this could be solved by upgrading vagrant to version 2.2.7 (bug 1795460) but there doesn't seem to be any activity in this area.

Assuming that this upgrade is non-trivial (bug 1811217) another solution would be to patch support in:

https://github.com/hashicorp/vagrant/commit/fb4e6985e142da56bad143d70600cd3695c91757

This patch is trivial, since nothing special is required to support VirtualBox 6.1 for a driver that already supports the 6.0 series:

https://github.com/oracle/vagrant-boxes/issues/178#issue-536720633

Version-Release number of selected component:

vagrant-2.2.6-1.fc31.noarch

I assume this is also true for Fedora 32 and Rawhide.

Steps to Reproduce:
1. Enable the rpmfusion free repository
2. Install the VirtualBox package
3. vagrant up --provider virtualbox <some box>

Actual results:
Can't start the VM :(

Expected results:
Can start the VM :)

Comment 1 Pavel Valena 2020-04-29 00:26:39 UTC
The update to Vagrant 2.2.7 will be coming shortly.

For detailed explanation, please see:
https://bugzilla.redhat.com/show_bug.cgi?id=1811217#c2


Note You need to log in before you can comment on or make changes to this bug.