Hi Jonathan, I responded to your support email yesterday - did you see my message?
I'll paste the contents here just in case: > Sorry that you're having trouble with the vagrant-vmware-fusion plugin. Let's > see if we can't get this sorted out for you. > > First of all, can you verify for me that you're running the latest version of > Vagrant? Running `vagrant --version` should report 1.7.2. > > If that looks good, can you send me a gist of the output of your failing > command with `VAGRANT_LOG=debug`? That should give me a lot more information > about what could be going wrong. > > It's looks like a pretty basic example that's failing, so I'm hopeful that the > issue is something simple and we'll have you up and running quickly. :) Happy to continue to help you out either here or on the support thread. Paul On Wed, Feb 11, 2015 at 8:10 AM, Jonathan Bayer <[email protected]> wrote: > I forgot the following: > > OSX Yosemite > Fusion 7 > > everything is fully up-to-date > > Fusion works well on it's own > > Thanks in advance > > > > On Wednesday, February 11, 2015 at 9:04:45 AM UTC-5, Jonathan Bayer wrote: >> >> We just purchased a license for the VMWare Fusion plugin. I installed >> the license, you can see that it is installed: >> [jbayer@Jonathans-MacBook-Pro aa]$ vagrant plugin list >> vagrant-share (1.1.3, system) >> vagrant-vmware-fusion (3.2.1) >> >> When I followed the instructions in the email to start a 64-bit Ubuntu >> box, I got the following error: >> [jbayer@Jonathans-MacBook-Pro aa]$ vagrant init hashicorp/precise64 >> A `Vagrantfile` has been placed in this directory. You are now >> ready to `vagrant up` your first virtual environment! Please read >> the comments in the Vagrantfile as well as documentation on >> `vagrantup.com` for more information on using Vagrant. >> >> [jbayer@Jonathans-MacBook-Pro aa]$ vagrant up --provider vmware_fusion >> Bringing machine 'default' up with 'vmware_fusion' provider... >> ==> default: Verifying vmnet devices are healthy... >> ==> default: Preparing network adapters... >> ==> default: Starting the VMware VM... >> An error occurred while executing `vmrun`, a utility for controlling >> VMware machines. The command and output are below: >> >> Command: ["start", "/Users/jbayer/Documents/Virtual >> Machines.localized/aa/.vagrant/machines/default/ >> vmware_fusion/65bf889d-5187-4ca9-92f8-d1b631a9d7a7/Sandbox.vmx", >> "nogui", {:notify=>[:stdout, :stderr]}] >> >> Stdout: Error: Cannot read the virtual machine configuration file >> >> Stderr: >> >> >> >> What I am really trying to do is package up a VMWare Fusion VM so I can >> distribute it to my developers. If I can get this going, we will most >> likely be purchasing between 20 and 30 more licenses. If I can’t get it >> going, then we (obviously) will not purchase any more. >> >> >> >> It seems that a .vmx and .vmxf file is needed, but the VMs I’ve created >> with Fusion 7 don’t have those files. >> > -- > 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/d/optout. > -- 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/d/optout.
