3.0.0

Version 3 removes support for python2. You'll need to make sure python3 is installed on your Mac.

Options for installing python3:

1. Install the pkg downloaded directly from python.org.
2. Install Apple's CL Tools (either by downloading the pkg from Apple's developer site, or by invoking the shim at /usr/bin/python3).
3. Build your own copy of python (E.g. Greg Neagle's relocatable python tools). You'll need to ensure that this custom python is the default python in your $PATH.

2.2.6

Updated to add an argument --disk_type

2.2.5

Fixes issue where vmware-vdiskmanager would crash due to a volume that wasn't mounted. Thanks to @zhaokai-vm for the fix!

2.2.4

Fusion 11.5 is out, so this release removes the beta bits.

2.2.3

Added to vmx:

board-id.reflectHost = "FALSE"

This keeps the VM from trying to use TouchID.

2.2.2

Fixes #59 where if a volume already existed at /Volumes/Recovery, vfuse would fail to figure itself out.

2.2.1

Bug fixes

2.2.0

This release:

• brings experimental catalina support (only qemu-img works for converting the dmg)
• is now prepped for python3
• removes unused code
• detects if Fusion isn't running, which is now required for using vmware-vdiskmanager

Fusion 11's tools don't seem to recognize the catalina dmg so use the qemu-img option.

2.0.9

This release brings full support for Fusion 11 on the vfuse side:

• hw_version will default to 16 now, which is what Fusion 11 supports.
• os_guest on 10.14 VMs will default to darwin18-64 instead of lying and claiming to be darwin17-64 which we were doing during the beta phase.

If you do not have Fusion 11 installed, and you install this version of vfuse, you'll want to pass --hw-version 14, or add that key to your templates.

For Fusion 11 users:

Note, that this issue still persists with Fusion 11, so if you are not using one of the workarounds mentioned here then you'll want to stick with 2.0.8 for the time being.

2.0.8

• Can now mix templates and -i
• Ability to configure qemi-img path
• Optional logging via templates