Mojave Compatibility

[dperaza83]

Hello. Apple just released macOS Mojave and I'm looking forward to switch to this new version of their OS. However, last time I checked the beta, there were some compatibility issues between VB and this OS. I'd like to know if these issues have been fixed for the release.

[socratis]

Are you talking about 10.14 as a guest? Because you posted on the "OSX Guests" section. If so, the answer is no; 10.14 is not yet supported as a guest.

[dperaza83]

I'm sorry I think posted to the wrong forum. I do mean 10.14, but as a host for my vagrant boxes.

[socratis]

I thought so. Moving to "OSX Hosts" from "OSX Guests".

So, what compatibility issues were you having exactly? There haven't been any issues after VirtualBox 5.2.14. And OSX 10.14 beta4 finally allowed VirtualBox to run (as long as it's 5.2.14 and later). Other than that there have been no reports of incompatibility.

[dperaza83]

I can't exactly remember what was the issue I was facing. I had to rollback the upgrade to High Sierra in order to be able to do my daily work. But I do remember it was something related to the "kext" or whatever that means.

Maybe the issue was already solved. I'm gonna try the upgrade on another machine and come back if I have any issues. Just wanted to hear from someone else who may have attempted the upgrade too.

[socratis]

Well, it just came out yesterday, and you're the first one to mention the 10.14 release version. For anything related to the betas, take a look at the section "VirtualBox on Mac OS X pre-releases".

But as I said, the only issue reported with 10.14 was a restriction that Apple put on VirtualBox. At the beginning (beta1) it was completely blacklisted, no questions asked. By the time that OSX hit 10.14 beta4, VirtualBox was at 5.2.14 and it had made the necessary changes that Apple wanted them. And as of 10.14 beta4 + VirtualBox 5.2.14, everything returned to normal.

Maybe that's the kext issue you remember; they were prohibited from loading.

[dperaza83]

Well I've performed the upgrade and everything looks fine so far. I just needed to upgrade VirtualBox and Vagrant as well as reinstalling any Vagrant plugin in place.

I'll report any issues I run into, if I find any.

[socratis]

I'll report any issues I run into, if I find any.

Just remember that Vagrant is not supported here, only VirtualBox, clean VirtualBox.

[Max Mac]

Hello, I have this issue with Mojave final version and with the latest VB version. There is a solutions? Thanks folk!

[socratis]

What issue would that be "Max Mac"? We didn't discuss any "issues" here...

[emilime93]

I can't find any definitive answer regarding Mojave Compatibility.
I currently rely on Kali Linux running in VirtualBox in my studies, but I'd like to install Mojave. On RoaringApps there is conflicting data regarding the compatibility. I couldn't find any information on VritualBox´s download page on what versions of macOS they support.
What I'm interested in is running the latest version of VB with Mojave. Could anyone confirm if it works running a Linux guest?

[socratis]

On RoaringApps there is conflicting data regarding the compatibility.

Citation needed. Because, if you mean that a person (scolson) reported incompatibility of 5.2.12 with 10.14, then you need to read this thread from the beginning. Carefully.

[dperaza83]

I'm running Centos 7. No problems so far.

[Draque]

UPDATE:

It turns out my problems came from a permissions setting that was reset. To anyone having this problem, go to System Prefs->Security & Privacy -> General -> Click the Allow button toward the bottom asking about Oracle dev tools. This solved my issues.

ORIGINAL TEXT

Just adding my story and what I've run into in the hopes that it might help... I just had to swap out my work computer due to a hardware failure, and am now running on a machine with OSX Mojave. All of my files/settings were pulled to the new machine, which is identical except for the new OS.

I have managed to get VirtualBox 5.2.18 itself running on my system, but am unable to open up any of my virtuals running. When I try to open them, I get this message:

Code: Select all

The virtual machine 'Windows 10' has terminated unexpectedly during startup with exit code (0x1).

Result Code: NE_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}

Kernal driver not installed (rc=-1908)

Make sure the kernal module has been loaded successfully.
VERR_VM_DRIVER_NOT_INSTALLED (-1908)
- The support driver is not installed. On linux, open returned ENOENT.

Note: New account, so it won't let me post a screen of the issue.

[socratis]

You migrated the apps/documents/preferences. But not the kernel drivers, those are tougher cookies, and usually non-transferable, you got to re-install the app. Otherwise you get:

Kernal driver not installed (rc=-1908)

It turns out my problems came from a permissions setting that was reset.

Technically, it wasn't reset. Since you changed OS versions and reinstalled, it wasn't "set" to begin with. Remember, the low level stuff are non-transferable.

System Prefs->Security & Privacy -> General -> Click the Allow button

That's the result of the stupidest mistake Apple ever made; trying superficially to increase security, and managed to screw up royally at the end. Known issue since the very first 10.13beta and with the workaround that you mentioned. Also documented in the sticky "Installation fails on 10.13.x (rc=-1908)".