Of course, you could have done this another way and renamed config.vm.box = 'base' $ cp -R hashicorp-VAGRANTSLASH-precise32 baseĪnd then you can go back and delete the 'hashicorp-VAGRANTSLASH-precise32' box as it is now a duplicate. Note that it is looking for the box named 'base'! So what I did is: $ cd ~/.vagrant.d/boxes You will see the following output: nfigure(VAGRANTFILE_API_VERSION) do |config| If you look inside the Vagrant file created for you: $ vim Vagrant However, assuming you setup a default Vagrant setup like so: $ cd ~/src/vagrant/myvm That last line is telling you that you have only one box, and its the precise32 box.

ĭrwxr-xr-x 4 some_user staff 136 Jun 29 13:23 hashicorp-VAGRANTSLASH-precise32/ You would see something like this: $ ls -laĭrwxr-xr-x 4 some_user staff 136 Oct 22 09:43. If you were to navigate to: ~/.vagrant.d/boxes I also realize you are targeting 'precise32', but i'm using 'base' as an example here. The underlying problem is that your VM machine is mislabeled. This is my machine setup: vagrant -v Vagrant 1.6.2 Puppet.manifests_path = 'puppet/manifests' V.customize Ĭonfig.vm.network :forwarded_port, guest: 3000, host: 3000 Override.vm.box = 'parallels/ubuntu-12.04' This is the Vagrantfile I have: # -*- mode: ruby -*-Ĭonfig.vm.provider 'vmware_fusion' do |v, override|Ĭonfig.vm.provider 'parallels' do |v, override| => default: Adding box 'base' (v0) for provider: virtualboxĪn error occurred while downloading the remote file. => default: Box 'base' could not be found. I am closing this issue, because libvirt provider is intended to be default for Fedora.I get this error when I do a vagrant up : ~ $ vagrant upīringing machine 'default' up with 'virtualbox' provider. Note that in order to install vagrant on Fedora properly, you should install package collection instead of 'vagrant' package solely. On the first line of your default Vagrantfile, which is located by default in '~/.vagrantd/'.

If you wish to change the default provider on your machine, simply putĮNV = 'virtualbox'

To enhance their libvirt experience we also set the default provider to libvirt. 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.įedora users are therefore encouraged to use libvirt provider, which is packaged in Fedora and working 'out of the box'.

Vagrant up provider virtualbox