The skinny :
To use VMware Fusion's vmrun from the command line (i.e. Terminal), you must invoke it with its FULL PATH, even if you are already in the same directory as vmrun lives in.
The fat :
Continuing to prove that VMware is great when it works and quite lousy when it doesn't, get this :
I opened Terminal.
I cd'ed to /Applications/VMware\ Fusion.app\Contents\Library.
I tried to execute "vmrun".
"Command not found"
How can that be?!! The command is definitely in that directory!
ls -l
Yup - there it is, vmrun, and all users have execute permission.
I lost probably half an hour on this stupid bug.
Turns out that the solution is simple, but horribly inobvious :
You must include the full path to vmrun every time you invoke it, even if you are already in the same directory as it!!!
So instead of bothering to cd to the enclosing directoy, just always use :
/Applications/VMware\ Fusion.app/Contents/Library/vmrun
Note : I tried adding the directory to my PATH to see if that way I could run vmrun just with "vmrun", but it didn't work.
Showing posts with label VMware Fusion. Show all posts
Showing posts with label VMware Fusion. Show all posts
Sunday, July 20, 2014
Subscribe to:
Posts (Atom)