Ticket #17805 (closed enhancement: fixed)

Opened 6 weeks ago

Last modified 20 hours ago

macOS 10.14 Mojave: VBoxDrv.kext < 5.3 Blocked By AppleKextExcludeList.kext

Reported by: jrtc27 Owned by:
Priority: minor Component: host support
Version: VirtualBox 5.2.12 Keywords:
Cc: Guest type: all
Host type: Mac OS X


After installing macOS 10.14 Mojave Beta 1 (18A293u), I can no longer use VirtualBox, as VBoxDrv.kext is blocked by AppleKextExcludeList.kext. Specifically, it is listed in its OSKextExcludeList blocking "LT 5.3". Presumably the kext needs modifications to work with the newer kernel.

Change History

comment:1 Changed 5 weeks ago by socratis

comment:2 Changed 5 weeks ago by IPv6Freely

Apple has closed bug report #41021597 with the following:

This is an issue for a third party to resolve based on the following:

The kext is blocked because it will panic the machine if allowed to load. Oracle is aware of what changes need to be made, it was communicated to them already. This is Oracle's issue to resolve, please contact them with any additional feedback.

We are closing this report.

If you have questions about the resolution, or if this is still a critical issue for you, then please update your bug report with that information.

Please be sure to regularly check new Apple releases for any updates that might affect this issue.


comment:3 Changed 5 weeks ago by janitor

  • Status changed from new to closed
  • Resolution set to invalid

macOS 10.14 Mojave is not yet supported.

comment:4 Changed 5 weeks ago by IPv6Freely

Mojave not yet being supported is kind of the point of filing the ticket.

comment:5 Changed 5 weeks ago by socratis

  • Status changed from closed to reopened
  • Resolution invalid deleted

Exactly what 'IPv6Freely' said. You can always tag it as "Suggestion/Enhancement".

Re-opening this. Otherwise please be fair and close all tickets that deal with forward looking kernels, be it Linux or NT.

Believe me, OSX 10.14 users are going to be a lot happier compared to the developers when this ticket is actually closed. Preferably as [Fixed]... ;)

comment:6 follow-up: ↓ 7 Changed 4 weeks ago by janitor

  • Priority changed from major to minor
  • Type changed from defect to enhancement

*shrug* Frankly I see zero real value in this ticket. We know Mojave will be out there and we are going to support it eventually, you don't have to tell us. Also there's nothing interesting you can tell us at this point about your situation w.r.t. Mojave. A typical bug about Linux kernel N+1 tells us about specific ways current VBox code fails on that kernel - usually a heads up on an API change. This bug literally just tells us that Mojave is not yet supported, which we know.

So is there any value in keeping this open besides psychotherapeutic? Not a rhetoric question. What kind of meaningful technical dialog do you expect to happen here?

comment:7 in reply to: ↑ 6 Changed 4 weeks ago by ShakiSHA

Replying to janitor:

*shrug* Frankly I see zero real value in this ticket.

Don't be so sad! In past updates, there wasn't needed any modification to adapt the essential compatibility of virtualbox with mojave.

This issue was made to help the community to identify that there is a problem and also where it is that.

So, is not zero real value. Be happy instead!

comment:8 Changed 3 weeks ago by IPv6Freely

A patched version was released for testing. See this forum post for the download URL:

To test this version, follow the instructions on this forum post:

This assumes you have SIP disabled on your system so that an unsigned kext will load.

comment:9 Changed 3 weeks ago by IPv6Freely

Updated procedure with kext dependencies fixed here:

comment:10 Changed 2 weeks ago by IPv6Freely

The new version 5.2.14 includes the fix for the kext. We're still waiting on Apple to update OSKextExcludeList from LT 5.3 to LT 5.2.14

comment:11 follow-up: ↓ 12 Changed 13 days ago by jrtc27

Indeed, I've been running with a kext built from trunk for the past week and it seems to be working just fine. On a related note, I submitted to the mailing list so that the kext would actually compile on Mojave; perhaps someone could review it, please?

comment:12 in reply to: ↑ 11 Changed 10 days ago by socratis

Replying to jrtc27:

On a related note, I submitted to the mailing list so that the kext would actually compile on Mojave; perhaps someone could review it, please?

I asked you a question on the mailing list, did you not get it? How are you actually going to build it if Macports for 10.14 isn't out yet?

I wouldn't want to continue the conversation on this thread as to avoid the noise, so either contact me via e-mail, or on the related thread on the forums:  Build VirtualBox ≥ 5.1.2 on OSX ≥ 10.9.

comment:13 Changed 8 days ago by IPv6Freely

silvae86 made a great write-up with full instructions on getting Virtualbox to run on MacOS Mojave while we wait for Apple to update their AppleKextExcludeList.kext:

comment:14 Changed 8 days ago by socratis

Please note a couple of remarks regarding the write-up:

comment:15 Changed 23 hours ago by michael

  • Status changed from reopened to closed
  • Resolution set to fixed

comment:16 Changed 20 hours ago by IPv6Freely

Just as a final note now that this ticket is closed:

Apple macOS Mojave Beta 4 now has VBoxDrv.kext set in the AppleKextExcludeList.kext as 'LT 5.2.14' which means VirtualBox will now install and run in Mojave without modification.

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use