Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#56063 - [vagrant] Does not support new VirtualBox 5.2

Attached to Project: Community Packages
Opened by Álvaro Castillo (sincorchetes) - Saturday, 21 October 2017, 06:25 GMT
Last edited by Levente Polyak (anthraxx) - Tuesday, 24 October 2017, 09:58 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Jonathan Steel (jsteel)
Levente Polyak (anthraxx)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

vagrant does not run at new VirtualBox version 5.2

Additional info:
* package version(s):

- vagrant 2.0.0-1
- virtualbox 5.2.0-1

* config and/or log files etc.


Steps to reproduce:

Launch vagrant up and It's tells does not compatible.

HOW TO SOLVE?

Download attachements and put this directories:
plugin.rb -> /opt/vagrant/embedded/gems/gems/vagrant-2.0.0/plugins/providers/virtualbox/
version_5_2.rb -> /opt/vagrant/embedded/gems/gems/vagrant-2.0.0/plugins/providers/virtualbox/driver/
meta.rb -> /opt/vagrant/embedded/gems/gems/vagrant-2.0.0/plugins/providers/virtualbox/driver/

If you get this issue:
################
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "da4577f4-3466-401a-bff0-b469e9dd1cbf", "--type", "headless"]

Stderr: VBoxManage: error: The virtual machine 'homestead-7' has terminated unexpectedly during startup with exit code 1 (0x1)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine
#################

That's you're upgraded VirtualBox but you are not built kmod modules:

HOW TO SOLVE?
sudo /sbin/vboxreload

SOURCE: https://github.com/hashicorp/vagrant/issues/9090

This task depends upon

Closed by  Levente Polyak (anthraxx)
Tuesday, 24 October 2017, 09:58 GMT
Reason for closing:  Fixed
Additional comments about closing:  2.0.0-2
Comment by Eli Schwartz (eschwartz) - Sunday, 22 October 2017, 02:18 GMT
https://github.com/hashicorp/vagrant/pull/8955#issuecomment-338034169 adding 5.2 support is already merged to master, and a release is planned by next week.

Loading...