dempson's Posts

I saw the same issue when I installed updates on my OS X Yosemite 10.10.5 VM, also in Fusion 8.5.8 on macOS 10.12.6 host: mouse and keyboard both stopped working inside the VM. For comparison, no such problem with the latest security update on a native Yosemite system running on my Mac mini (2012). Also no problem with the latest updates in VMs running OS X El Capitan 10.11.6 and macOS Sierra 10.12.6. One detail of note: my Yosemite VM is using the Der Flounder BeamOff technique to improve UI performance in the Yosemite VM, but this is set up to run via a LaunchAgent, which doesn't kick in until after the login window. I wasn't able to get that far because I couldn't move the mouse or type anything in Yosemite's login window. Investigation so far: 1. Restored my backup of the Yosemite VM, then installed all available updates apart from Security Update 2017-003. Still works, so it definitely looks like the security update. (I note that the iTunes 12.6.2 update is not offered on Yosemite until after this security update has been applied, but I never got that far on my first attempt to install updates, and I doubt iTunes would have such a wide impact on the system.) 2. Took a snapshot of the VM. 3. Set up Remote Management in System Preferences and confirmed I can remotely control the VM using Remote Desktop from my host Mac, including entering password in the OS X login screen. 4. Installed the security update again. After restart, again confirmed that the keyboard and mouse are not working in the VM. 5. Used Remote Desktop. It can control Yosemite in the VM, therefore the problem is only that VMware Fusion 8.5.8 is not able to forward keyboard/mouse activity to the VM. 6. Just in case, I did a Reinstall VMware Tools. It didn't help. As I use this VM rarely, I'm happy to leave it in this "indirectly usable" state for now, if there is anything else that someone would like me to try or there is anything useful I can gather from it.

Mostly a side note for clarification: the error message about "AppleUSBEthernetHost.kext" is not relevant to problems with USB storage devices. That kernel extension is installed or updated by iTunes (as well as an initial version being installed as part of OS X). It provides support for using an iPhone (or cellular iPad) as a personal hotspot via USB. It also supports Apple's USB Ethernet adapter. There has been a recurring problem where Apple has included a version of this kernel extension in the iTunes installer which works fine on recent major OS X versions supported by iTunes, but is broken on older OS X versions. For example, iTunes 11.4 is able to be installed on OS X 10.6.8 and later, but the copy of this kernel extension it installs only works on OS X 10.8 and later. The problem can be fixed by deleting the incompatible kernel extension, locating an older iTunes installer (e.g. iTunes 10.7), and using the third party utility Pacifist to manually install AppleUSBEthernetHost.kext from the older iTunes. This kernel extension is not involved in accessing USB storage devices, so installing an older (working) version of AppleUSBEthernetHost.kext is not likely to help with any compatibility issues VMware Fusion 8.5 may be having with USB 3.0 storage devices and Snow Leopard guests.

I've just got around to installing VMware Fusion 8.0.1 (upgrading from version 7) and ran into the same problem: installation of the tools failed in all VMs running OS X 10.5 through 10.7 (so far, and I expect I'll have the same issue when I update my 10.8 through 10.10 VMs), reporting an error with the postinstall script. I had a look inside the postinstall script using Pacifist and have a theory as to the reason for the error. The script ends with this: # Up to Mac OS 10.11 Developer Beta 2 (15A204h), mount(8) searches for # mount_<fs> in the following locations, in this order: #    /sbin/mount_<fs> #    /usr/sbin/mount_<fs> #    /System/Library/Filesystems/<fs>.fs/Contents/Resources/mount_<fs> # # Starting with Mac OS 10.11 Developer Beta 1 (15A178w), System Integrity # Protection is enabled so even root cannot write to any of these locations. # # Starting with Mac OS 10.11 Public Beta 1 (15A215h), mount(8) searches for # mount_<fs> in this 4th location, which root can write to: #    /Library/Filesystems/<fs>.fs/Contents/Resources/mount_<fs> mkdir -p /Library/Filesystems/vmhgfs.fs/Contents/Resources ln -s '/Library/Application Support/VMware Tools/mount_vmhgfs' \    /Library/Filesystems/vmhgfs.fs/Contents/Resources/ if [ "$macosMajor" -lt 15 ]; then    ln -s '/Library/Application Support/VMware Tools/mount_vmhgfs' /sbin/ fi I ran each command manually and they all worked except the last one, which creates a symbolic link in sbin. $ sudo ln -s '/Library/Application Support/VMware Tools/mount_vmhgfs' /sbin/ Password: ln: /sbin//mount_vmhgfs: File exists The earlier version of the VMware Tools had copied mount_vmhgfs to /sbin/ rather than creating a symbolic link. Replacing it with a symbolic link requires removing the previous file first.