Yeah. I figured as much, but didn't know where else to start.
On Friday, March 22, 2013 10:24:44 AM UTC-5, Mitchell Hashimoto wrote:
`config.vm.customize` used "VBoxManage." VBoxManage is VirtualBox-specific, so that is not supported for VMware Fusion, obviously. :)
I don't know the answer to your question but I just wanted to point that out.
Does anyone have or know of the Vagrantfile config to add a second vmdk to a VM? I've tried the old vbox syntax, and that seems to make Vagrant angry.
~/Vagrantfile:21:in `block (5 levels) in <top (required)>': undefined method `customize' for #<HashiCorp::VagrantVMWareFusion::Config:0
You received this message because you are subscribed to the Google Groups "Vagrant" group.
For more options, visit https://groups.google.com/groups/opt_out.
Mitchell, I know you said there are no plans for this kind of support. However, if it can be considered for a future major release (1.0, 1.1), it would be great to completely get rid of our reliance on the Fusion GUI.