The official documentation has support for Linux, macOS and Windows on how to find and use the vmrun command.Īlias vmrun="/Applications/VMWare\ Fusion.app/Contents/Library/vmrun" I’ve opted to make a simple BASH alias ( on macOS, in my case ) to use it without referencing its full path. On your specific system, you will need to find where the command is installed to use it. Because it has quickly become one of my most-used commands. No one ever told me about the vmrun command. So, while I understand Vagrant and VMware are not competing products ( you can even use VMware with Vagrant ) - I wanted to bring that Vagrant-like, scriptable workflow to my VMware experience without even using Vagrant. It hurts because I really like automation. I’ve seen this in the classroom so many times, it hurts. What I mean by this is: it’s typical that you won’t find many people scripting their VMware workflow… or genuinely taking an absurd amount of pride in manually doing this tedious work. This is fine, but not ideal for everything.Ĭompared to the workflow that tools like Vagrant provide, I tend to find VMware to be far less command-line workflow focused. Practically every intro book will show you how to poke around the GUI to start, stop, and generally manage the various different VMs you have running. When first introduced into the world of V irtual Machines, one might find themselves working with the popular VM solution VMware.
0 Comments
Leave a Reply. |