Changes between Version 6 and Version 7 of Ticket #19963, comment 3
- Timestamp:
- Feb 22, 2021 1:54:01 PM (3 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #19963, comment 3
v6 v7 1 1 Note that the VirtualBox (VBox) 6.x installer also comes with its own FUSE for macOS (OSXFUSE) installer, which runs by default {the third screen has a Customize button at lower left, via which you can opt out}. That bundled FUSE installer also now seems to place its components directly into '/Library/…' and '/usr/local/…'. Perhaps VBox is most compatible with that bundled version? 2 2 3 {Hmm, come to think of it, I'm not entirely sure about that bundled version's compatibility with (especially for new installations on) macOS 10.13.2 'High Sierra' & later, where there might be various issues related to loading kernel extensions such as the one used by OSXFUSE & all its later renamed editions (e.g., the whole dance with "System Preferences > Security & Privacy => 'Allow' button that maybe shows up & works if we're lucky"). But I'll plough on ahead anyway …}3 {Hmm, come to think of it, I'm not entirely sure about that bundled version's compatibility with macOS 10.13.2 'High Sierra' & later (especially for new installations), where there might be various issues related to loading kernel extensions such as the one used by OSXFUSE & all its later renamed editions (e.g., the whole dance with "System Preferences > Security & Privacy => 'Allow' button that maybe shows up & works if we're lucky"). But I'll plough on ahead anyway …} 4 4 5 5 FWIW, VBox 6.1.18's vboximg-mount works well on my host Mac under macOS 10.13.6 'High Sierra'. I'm also a long-time user of initially MacFUSE {big 'M' (legacy)} and later OSXFUSE / FUSE for OS X / FUSE for macOS / macFUSE {little 'm' (latest renaming)}, independently of VBox. So, I have my own installation of macFUSE 4.0.5, along with what I recently noticed is an older OSXFUSE 3.10.4 that (presumably) VBox installed afterwards. However, I've also noticed that the macFUSE installer can try to remove all traces of OSXFUSE, so it's also possible that installing it after installing VBox could lead to this issue.
