[Fixed] 5.2.12 install fails on macOS Mojave (#17805)

[baconCheeseFry]

Hold up. I went back and completely removed the VboxDrv section from the info plist instead of setting it to 'LT 5.2' and now it installed. I can't open the app because it says `You can’t use this version of the application “VirtualBox.app” with this version of macOS. You have "VirtualBox.app 5.2.13". However, my homestead/vagrant box comes up so I guess I am good.

[noplacelike::1]

Thanks! Working again for me.

ss.png (98.42 KiB) Viewed 40876 times

[IPv6Freely]

Same result.

I modified the kext Info.plist to be 5.4.12 (picked arbitrarily) instead of 5.2.12, and the kext now loads. I get the same error when I try to load the virtualbox GUI via Launchpad:

Screen Shot 2018-06-27 at 9.43.49 AM.png (48.48 KiB) Viewed 40872 times

However, If I run VirtualBox from the CLI, the GUI opens and I can now start VMs. That clearly explains exactly why it's now working in Vagrant for the previous poster. I'd add a screenshot but max filesize on this forum is 128KB

Looks like we have a working patch! I checked the source tree repo and it looks like this patch must have come from a development branch that isn't available to view for us peons. Can you shed some light on what was changed?

Unfortunately because of Apple's exclude kext it, Oracle is going to have to release this as 5.3 which is a bit silly for a minor revision, but it is what it is...

[IPv6Freely]

For those who want to try the new patch, install as usual (the installation will fail) and then do the following:

Code: Select all

sudo sed -i '' 's/5\.2/5\.3/g' '/Library/Application Support/VirtualBox/VBoxDrv.kext/Contents/Info.plist'

sudo kextload '/Library/Application Support/VirtualBox/VBoxDrv.kext'

kextstat -bundle-id org.virtualbox.kext.VBoxDrv

VirtualBox &

This assumes you have SIP disabled on your system (using csrutil disable from Recovery mode) so that an unsigned kext will load.

[socratis]

Unfortunately because of Apple's exclude kext it, Oracle is going to have to release this as 5.3 which is a bit silly for a minor revision, but it is what it is...

Or, Apple can remove the exclusion in their next release (or make it < 5.2.12 | 5.1.38) , once they see that VirtualBox implemented the changes that they were blocking VirtualBox in the first place...

[IPv6Freely]

Yup, also possible assuming that communication is there

[Yaroon]

Unfortunately changing the version number doesn't fix it completely.

Code: Select all

sudo kextload "/Library/Application Support/VirtualBox/VBoxDrv.kext"

might work... but a subsequent

Code: Select all

sudo kextload "/Library/Application Support/VirtualBox/VBoxUSB.kext"

or

Code: Select all

sudo kextload "/Library/Application Support/VirtualBox/VBoxNetAdp.kext"

does not.

It will fail with:

Code: Select all

/Library/Application Support/VirtualBox/VBoxUSB.kext - dependency 'org.virtualbox.kext.VBoxDrv' not found.
Diagnostics for /Library/Application Support/VirtualBox/VBoxUSB.kext:
Dependency Resolution Failures: 
    No kexts found for these libraries: 
        org.virtualbox.kext.VBoxDrv

because these kexts are looking for VBoxDrv 5.2.13, not 5.3.13.

[mkc]

You need to change dependency versions in other kexts as well to match 5.3.13.
After doing so, still you might notice that

Code: Select all

sudo kextload "/Library/Application Support/VirtualBox/VBoxUSB.kext"

will fail.

In that case you can try:

Code: Select all

sudo kextutil -r /Library/Application\ Support/VirtualBox -bundle-id org.virtualbox.kext.VBoxUSB

which loaded the extension in my case.

[Yaroon]

Thank you mkc, that was indeed it.

I had changed the dependency versions but kextload wouldn't load them. I had not thought (nor did I know) about kextutil -r

Thanks again. It still bugs me very much though that I don't know how to edit AppleKextExcludeList and have the changes become effective. Not even with `kextcache -i /` which seemed to rebuild all the kext caches.

[mkc]

It still bugs me very much though that I don't know how to edit AppleKextExcludeList and have the changes become effective. Not even with `kextcache -i /` which seemed to rebuild all the kext caches.

This assumes you have SIP disabled on your system (using csrutil disable from Recovery mode) so that an unsigned kext will load.

[Yaroon]

Yeah, that's the case mkc

Code: Select all

$ csrutil status
System Integrity Protection status: disabled.

It's strange, I don't get it.

[Canuk In Augusta]

Any idea when the patch will be released as an official release and be able to be run/Installed in Mojave without turning of system integrity?

[IPv6Freely]

Any idea when the patch will be released as an official release and be able to be run/Installed in Mojave without turning of system integrity?

Well, there's no real rush since the only people who would be running Mojave are developers anyway. So as long as it's out before Mojave comes out of Beta (late September, usually) it's fine

[IPv6Freely]

Sorry guys, I should have mentioned the other kexts. Just use the commands from the postflight script (https://www.virtualbox.org/browser/vbox ... postflight):

Code: Select all

sudo sed -i '' 's/5\.2/5\.3/g' '/Library/Application Support/VirtualBox/VBoxDrv.kext/Contents/Info.plist'
sudo sed -i '' 's/5\.2/5\.3/g' '/Library/Application Support/VirtualBox/VBoxUSB.kext/Contents/Info.plist'
sudo sed -i '' 's/5\.2/5\.3/g' '/Library/Application Support/VirtualBox/VBoxNetAdp.kext/Contents/Info.plist'
sudo sed -i '' 's/5\.2/5\.3/g' '/Library/Application Support/VirtualBox/VBoxNetFlt.kext/Contents/Info.plist'

sudo kextload '/Library/Application Support/VirtualBox/VBoxDrv.kext'
sudo kextload -d '/Library/Application Support/VirtualBox/VBoxDrv.kext' '/Library/Application Support/VirtualBox/VBoxUSB.kext'
sudo kextload -d '/Library/Application Support/VirtualBox/VBoxDrv.kext' '/Library/Application Support/VirtualBox/VBoxNetFlt.kext'
sudo kextload -d '/Library/Application Support/VirtualBox/VBoxDrv.kext' '/Library/Application Support/VirtualBox/VBoxNetAdp.kext'

Virtualbox &

[IPv6Freely]

Thanks again. It still bugs me very much though that I don't know how to edit AppleKextExcludeList and have the changes become effective. Not even with `kextcache -i /` which seemed to rebuild all the kext caches.

I had been thinking about this, but honestly I'd feel better about editing the kext of a 3rd party application instead of a system kext. This works well enough, for now.