Changing the default VM Path in VMWare Fusion on OSX Yosemite: I had a little trouble figuring this out - so making a note of it. The VMWare Fusion default location for VMs is /Documents/Virtual Machines.localized, which doesnt work well for me as I typically have Documents symbolically linked to my Dropbox directory and prefer to move the default VM location rather than manage exclusions on every Dropbox install I have. It's relatively straightforward on VMWare Workstation, and Oracle VirtualBox - but for some reason not well documented in VMWare Fusion. Turns out it's relatively simple to update, so here it is so I don't forget the next time I need to do this. Saving as a public gist in case it's of value for anyone else. I'm using VMWare Fusion v6, haven't tested on other versions - but I suspect it'll work on them.
OS X boots without the need for unlocking VMWare. That's right. I was able to actually install Yosemite natively, using Plop Boot Manager (to boot from usb). The installation goes without a hitch. Just like VMWare Workstation version 10, EFI boot works flawlessly. We can allocate more than 128MB of VRAM to VM Guests. Mac OS X El Capitan 10.11.6 VMware Image Free Download Latest For Mac. Its full bootable ISO image of Mac OS X El Capitan 10.11.6 VMware Image. Mac OS X El Capitan 10.11.6 VMware Image Overview. Apple has recently released the 6 th update for its El Capitan operating system which was originally released in September 2015. Mac OS X El Capitan 10.
![Yosemite Yosemite](http://www.weatherhead.net/myhome/wp-content/uploads/2014/12/VMFusion_Version.png)
Need to test this. Changing the default VM Directory for VMWare Fusion Open up /Library/Preferences/VMWare Fusion/preferences in your favorite text editor cd /Library/Preferences/VMWare Fusion cp preferences preferences.backup vi preferences Look for a line starting with prefvmx.defaultVMPath. If it is present in the file, update the directory assigned to it to the new default VM directory. If it's missing, add it to the bottom of the file and save your work.
Quit VMWare Fusion if it is running. Start VMWare fusion and attempt to create a new VM, anything will do. Once done - check that the files have ended up in the new default VM directory. Finally - quit VMWare Fusion again, and move the contents of /Documents/Virtual Machines.localized to your new default VM directory. Cd /Users/MYUSERNAME/VirtualMachines/VMWareFusion mv '/Users/MYUSERNAME/Virtual Machines.localized/.'
./ rmdir '/Users/MYUSERNAME/Virtual Machines.localized' Start VMWare Fusion again and you should see any pre-existing VMs available in the Virtual Machine manager. update 20jan17: after working fine for a couple of weeks Fusion suddenly lost all VM's. Rather than fight it, going back to default setup. So don't trust what I posted below;-) I copied the 'Virtual Machines.localized' directory to another disk, renamed the original, then I had to add 'prefvmx.defaultvmpath' (all lower case) to the file, and then had to use the 'open recent' menu to get fusion to open them. Sierra 10.12.2 and vmware fusion 8.5.3. When the parameter was prefvmx.defaultVMPath with uppercase it seemed to be ignored. This folder does not exist in VMWare Fusion v10.
There is a /Library/Application Support/VMware Fusion/, but it's empty. E: It appears it doesn't create the /Library/Preferences/VMware Fusion/ folder until after the first virtual machine is created and ready to launch. I did, however, direct it to save the VM outside of iCloud Documents, in the Virtual Machines.localized that it created, which I had already moved out of Documents.
I can now use the configuration option in case I need to create future virtual machines. E2: I just opened the preferences file, only to discover that it had already changed the prefvmx.defaultVMPath setting to match the newly moved Virtual Machines.localized folder.
The signs of fall are beginning to appear: The evenings are a little cooler; leaves are beginning to turn; bulky people are tossing leather spheroids through the air; and VMWare and Parallels are releasing new versions of their Mac virtualization apps. Every year around now, the two companies come out with updates to VMware Fusion and Parallels Desktop, both of which do pretty much the same thing: Enable you to run Windows (or other desktop operating systems, including older versions of OS X itself) on your Mac. We’ve already seen a couple of weeks ago. And now VMware has released.
The only trick to these annual releases is that each year there’s less and less new stuff for the two programs to do. (We'll be doing our soon.) This year, the marquee features in VMware Fusion 7 are all about compatibility with OS X Yosemite (which primarily means cosmetic things like streamlined toolbars and more translucency).
![Yosemite Yosemite](http://blogs.vmware.com/teamfusion/files/2015/01/Yosemite-VM-on-Yosemite.jpg)
The new Fusion also boasts improved compatibility with some hardware features found in the latest Macs, including the ability to tap into up to 2GB of video memory and optimization for the latest Haswell chips from Intel. (The company also says the software will be ready for Intel's next generation Broadwell chips, when those hit the Mac.) VMware says the new version is 11 percent faster in multimedia tests overall, with even better performance in some specific tasks (such as video encoding). At the same time, the software is supposedly more energy efficient, and it wakes up faster from an idle state. Meanwhile, the Pro version of Fusion 7 can run a greater range of operating systems (more than 200, says VMware) and supports iSight cameras in virtual machines. It can also connect to the company's vSphere servers, which run virtualized operating systems remotely. VMware Fusion 7 and VMware Fusion 7 Pro are available today for $70 and $150 respectively.
If you’re running Fusion 5 or 6 now, it’ll cost you $80 to upgrade (unless you purchased version 6 after August 1 of this year, in which case the upgrade is free).