VB 6.0.2 and 6.0.4 installation fails on macos 10.13.6

[wgd]

This is not a security/KEXT problem (directly, at least).

Trying to install VirtualBox 6.0.2 a week ago and again today with 6.0.4, ran into an issue where the install would get all the way through until the last screen reported Installation Failed. The workaround I found was to do an Advanced install and deselect the FUSE option. Unfortunately, this seems to defeat the point of having updated to the 6. series, other bug fixes, &c aside.

Attached is the install.log which shows both the 6.0.2 and 6.0.4 install attempts. Both were ultimately successful once I deselected the FUSE option.

[wgd]

/var/log/install.log (6.0.4 install extract)

[wgd]

/var/log/install.log (6.0.2 install extract, plus following log entries)

[wgd]

A quick grep in the full install.log shows that the FUSE component had been installed (and presumably working) with the initial install, performed with whatever was current at the time on 2018-07-28 and again with a subsequent update on 2018-12-13:

$ grep -n FUSE install.log     
1633:2018-07-18 13:03:10+04 Admins-MacBook-Pro installd[455]: ./postinstall: installing/upgrading FUSE to osxfuse_3.7.1.pkg
1660:2018-07-18 13:03:11+04 Admins-MacBook-Pro installer[5322]: Installed "FUSE for macOS" ()
1690:2018-07-18 13:03:12+04 Admins-MacBook-Pro installd[455]: ./postinstall: installer: Package name is FUSE for macOS
1693:2018-07-18 13:03:12+04 Admins-MacBook-Pro installd[455]: ./postinstall: installation/upgradation of FUSE to osxfuse_3.7.1.pkg is complete
64969:2018-12-13 13:12:59-07 MacBook-Pro installd[66953]: Installed "FUSE for macOS" ()
$ 

[Socratis]

Did you have OSXFUSE on your computer before attempting to install VirtualBox 6.0.x? In my case I've been having OSXFUSE since for ever, so I never realized, not even during the 6.0beta cycle that OSXFUSE was being installed as part of VirtualBox.

On the other hand, we're now up to 6.0.4 and you're the first such complaint that I've seen. My guess? Wrong/improper permissions with your filesystem. But we'll need to investigate it.

This is the typical filesystem permissions that I usually ask people to check for in the pre-6.0.x era. Now I got to see where OSXFUSE gets installed and add those dirs to the list-to-check:

ls -laed@ \
  / \
  /Applications \
  /Applications/VirtualBox.app \
  /Applications/VirtualBox.app/Contents/MacOS/VirtualBox \
  /Applications/VirtualBox.app/Contents/MacOS/VirtualBoxVM \
  /Applications/VirtualBox.app/Contents/MacOS/VBoxRT.dylib \
  /private \
  /private/etc \
  /private/etc/sudoers \
  /private/tmp

[Socratis]

BTW, it's usually better and faster, if issues get first addressed in the ​VirtualBox forums, a lot more eyes there. More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of, if the issue is resolved in the forums first.

[wgd]

Thank you for the update, socratis.

Here is the requested info:

$ ls -laed@ \
> / \
> /Applications \
> /Applications/VirtualBox.app/ \                                                                                                  
> /Applications/VirtualBox.app/Contents/MacOS/VirtualBox \
> /Applications/VirtualBox.app/Contents/MacOS/VirtualBoxVM \
> /Applications/VirtualBox.app/Contents/MacOS/VBoxRT.dylib \
> /private \
> /private/etc \
> /private/etc/sudoers \
> /private/tmp
drwxr-xr-x  36 root  wheel      1152 Feb 11 16:06 /
drwxrwxr-x+ 77 root  admin      2464 Jan 31 10:32 /Applications
 0: group:everyone deny delete
drwxr-xr-x   3 root  admin        96 Jan 28 12:41 /Applications/VirtualBox.app/
-rw-r--r--   1 root  admin   5903952 Jan 25 10:46 /Applications/VirtualBox.app/Contents/MacOS/VBoxRT.dylib
-rwxr-xr-x   1 root  admin  33067904 Jan 25 10:46 /Applications/VirtualBox.app/Contents/MacOS/VirtualBox
-rwsr-xr-x   1 root  admin    157264 Jan 25 10:46 /Applications/VirtualBox.app/Contents/MacOS/VirtualBoxVM
drwxr-xr-x   6 root  wheel       192 Mar 27  2018 /private
drwxr-xr-x  93 root  wheel      2976 Feb 13 20:06 /private/etc
-r--r-----   1 root  wheel      1602 Jul 18  2018 /private/etc/sudoers
drwxrwxrwt  27 root  wheel       864 Feb 13 21:58 /private/tmp

Regarding the forums., I will definitely keep that in mind for future requests! I had searched for similar issues but not found any at the time. I had seen another article on working around various VirtualBox installation issues: ​https://medium.com/@DMeechan/fixing-the-installation-failed-virtualbox-error-on-mac-high-sierra-7c421362b5b5 (which I also responded to: ​https://medium.com/@mrdavies/still-didnt-work-91291995129).

Anyway, thanks again and perhaps I have a simple problem with the install?

[Socratis]

Your permissions look fine. But those are the ones mainly for VirtualBox. As I said on a previous comment:

Now I got to see where OSXFUSE gets installed and add those dirs to the list-to-check

And I found them:

ls -laed@ \
  /Library \
  /Library/Filesystems \
  /Library/Frameworks \
  /usr/local/lib

For reference, here's what I get on mine, see if they match with yours:

$ ls -laed@ \
>   /Library \
>   /Library/Filesystems \
>   /Library/Frameworks \
>   /usr/local/lib
drwxr-xr-x+ 63 root  wheel  2142 24 Απρ  2018 /Library
 0: group:everyone deny delete
drwxr-xr-x   4 root  wheel   136 11 Φεβ 11:49 /Library/Filesystems
drwxr-xr-x  17 root  wheel   578 13 Φεβ 17:40 /Library/Frameworks
drwxr-xr-x  30 root  wheel  1020 11 Φεβ 11:49 /usr/local/lib

I had another idea; install OSXFUSE as a standalone package, see how that goes. It's the exact same thing that VirtualBox includes in their package. Get it from ​https://osxfuse.github.io/

There's OSXFUSE version 3.8.3 available (as of this writing), VirtualBox 6.0.4 comes with OSXFUSE 3.8.2. There's no problem, I've installed/tried both. Either will do...

[wgd]

Good deal! Thanks for that update. I will check that out and update ASAP.