I am trying to set up a suite of vm's, which I want to only vmware_fusion
I had hoped that by setting  config.vm.provider = "vmware_fusion" in my 
Vagrantfile, I could create an instance simply with 'vagrant up'

But each time it complains about VirtualBox, unless I also pass 
provider=vmware_fusion on the commandline
The base box has a metadata.json containing only vmware_fusion, and my 
Vagrantfile specifies vmware_fusion too.

It seems like it would make more sense if vagrant could deduce that the 
necessary provider is vmware_fusion, instead of pestering me with 
VirtualBox messages and forcing me to specify provider on commandline.

Is this by design, or a legacy issue from when vagrant was VirtualBox-only?



My config is like...

config.vm.box = "centos6_minimal"
config.vm.provider = "vmware_fusion"
config.vm.box_url = "http://url/vagrant-centos-6.4-x86_64-vmware_fusion.box";

Granted, Its not a huge issue to pass it on cmdline, but Id like to 
understand why its even necessary

Thanks for any advice.

-- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to