Bug 1829060

Summary:	Add VirtualBox 6.1 support to Vagrant
Product:	[Fedora] Fedora	Reporter:	Dridi Boukelmoune <dridi.boukelmoune>
Component:	vagrant	Assignee:	Pavel Valena <pvalena>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	31	CC:	dridi.boukelmoune, lmohanty, madam, pvalena, strzibny, thrcka, vondruch
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-04-29 00:26:39 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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