Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

fission start does not work with VMWare Fusion 4 #20

Closed
danielqo opened this Issue Apr 27, 2012 · 1 comment

Comments

Projects
None yet
2 participants

fission start VMNAME implicitly refers to /Library/Application Support/VMware Fusion/vmrun VMWare utility to start a given VM. However, since VMWare Fusion 4, vmrun is now part of the VMWare Fusion.app bundle (whose current path is /Applications/VMware Fusion.app/Contents/Library/vmrun), causing the following error to the fission startcommand:

Starting 'FOO_VM'
sh: /Library/Application Support/VMware Fusion/vmrun: No such file or directory
There was a problem starting the VM.  The error was:

So, the current best workaround this issue is to create a file named .fissionrc at your home directory (~/.fissionrc) with the following content:

vmrun_bin: "/Applications/VMware Fusion.app/Contents/Library/vmrun"

This will override the default settings at fission/config.rb file.

Owner

thbishop commented May 11, 2012

Hi Daniel,

You're absolutely correct. I've updated the README (2d5dd30) with information about this. Hopefully, the update will help others.

@thbishop thbishop closed this May 11, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment