Hide Forgot
Description of problem: vagrant up on a fresh installation of Vagrant defaults to trying to spin up a libvirt provided virtual machine. This goes against default behavior of Vagrant (documented [here](https://www.vagrantup.com/docs/providers/default.html)) which is to default to virtualbox. How reproducible: Always Steps to Reproduce (without a working version of libvirt installed): 1. dnf install vagrant 2. vagrant init ubuntu/trusty64 && vagrant up Actual results: It should start up a virtual machine in Virtualbox. Expected results: The provider 'libvirt' could not be found, but was requested to back the machine 'default'. Please use a provider that exists. Additional info: I assume this has to do with VirtualBox not being available in core Fedora repos, but in the instance of a fresh install of Fedora (neither libvirt or VirtualBox installed) I would expect that vagrant up would result in a "provider 'virtualbox' could not be found".
Hi Dan, yes, VirtualBox cannot be packaged for Fedora (the kernel module for VirtualBox is not part of the upstream kernel) and needs installation from other sources. Fedora users are therefore encouraged to use libvirt provider, which is packaged in Fedora and working 'out of the box'. To enhance their libvirt experience we also set the default provider to libvirt. If you wish to change the default provider on your machine[1], simply put ``` ENV['VAGRANT_DEFAULT_PROVIDER'] = 'virtualbox' ``` on the first line of your default Vagrantfile, which is located by default in "~/.vagrantd/". Note that in order to install vagrant on Fedora properly, you should install '@vagrant' package collection[1] instead of 'vagrant' package solely. I am closing this issue, because libvirt provider is intended to be default for Fedora. [1] https://developer.fedoraproject.org/tools/vagrant/vagrant-virtualbox.html [2] https://developer.fedoraproject.org/tools/vagrant/vagrant-libvirt.html