Signum 11 is a segmentation fault, which is definitely a bug in Fusion. It could be bad handling of a configuration error you have in your setup or a problem you can do nothing about until they fix ...
See more...
Signum 11 is a segmentation fault, which is definitely a bug in Fusion. It could be bad handling of a configuration error you have in your setup or a problem you can do nothing about until they fix it. If you haven't already, look at the fs type and mount options for the external disk and make sure it isn't setup as a removable device. Here are the mount type and options for my home directory on my older, macbook pro 2014 vs macbook air 2000-m1: 2014 macbook pro: apfs, local, journaled, nobrowse 2020 macbook air m1: apfs, local, journaled, nobrowse, protect To make sure you are looking at the correct disk partition: cd ~ df . # look for the disk at the start and grep for it in mount replacing my entry: mount | grep /dev/disk3a5 The VMWare Fusion v12 is installed on my Macbook Pro. A couple years ago, I moved nearly everything off but left VMWare Fusion and my Linux VM. I updated fusion too. It was a hack job, where I may have removed contents under Library/Preferences. My Linux VM runs and mounts hgfs, but clipboard doesn't work. It gets a lot of the same issues of not finding files as in your log, but neither of the warnings -- even without having an /etc/vmware/hostd file. The only file it does appear to read is ~HOME/Library/Preferences/VMware\ Fusion/preferences, where your log doesn't list this file. The differences are likely in the version of Fusion. I have a Mac-mini with Fusion at home, so can check out the logs when I'm back there later. Hope this helps. I'm just a user of VMWare, but had a recent issue so thought I'd pitch in to help.