Submitted [email protected]

“You can use the vmrun command line utility to control virtual machines and automate guest operations.”

Further information

The vmrun command is much like the days when us techies used to dabble with the vmware-cmd command in ESX v2.x & v3.x to assist with BASH scripts for backups and snapshots. Ahh, those were the days… All manner of tasks could be completed with Virtual Machines and the control was entirely at your finger tips and not the GUI. Anyway, back to this article.

As of Fusion v4 the location of the vmrun command and other utilities were moved from the /Library/Application Support/ VMware Fusion directory to the /Applications/VMware Fusion.app package file. Many postings over time have appeared querying the location and explaining where it’s moved to. Ironically here I am adding to this pile of search engine results ;-)

If you’re using Fusion v4 and want to use vmrun then every time you issue a command you’ll need to provide the fully directory path. Not ideal but workable however; you could add the directory path to your system. To do this open a Terminal session and issue the command:

export PATH=”$PATH:/Applications/VMware Fusion.app/Contents/Library”

for Tech Preview users use this:

export PATH=”$PATH:/Applications/VMware Fusion Tech Preview.app/Contents/Library”

Here’s a screenshot taken from within my Terminal session.

Setting the path

Setting the path

As you can see to prove it’s worked I’ve issued the command vmrun list to reveal all running VMs on my Mac.

For a full list of supported vmrun syntax and available options just execute the vmrun command within a Terminal session. Also, the PDF published by VMware can assist with more explanations but it’s a little out of date. http://www.vmware.com/pdf/vix162_vmrun_command.pdf

Thanks Steve.

If you have a VMware Fusion tip you’d like to share click the iVitualise Sticker menu item and complete the form. I’ll post you a couple of stickers to say ‘thank you’.