VirtualBox

Ticket #18024 (closed defect: duplicate)

Opened 4 years ago

Last modified 3 years ago

Installation fails on new Mojave install MacOS 10.14 -> duplicate of #18645

Reported by: JasonMc Owned by:
Component: installer Version: VirtualBox 5.2.18
Keywords: Cc:
Guest type: other Host type: Mac OS X

Description

The installer fails running postflight to register the VBoxDrv.kext.

Oct 1 08:46:03 imac installd[370]: ./postflight: /Library/Application Support/VirtualBox/VBoxDrv.kext failed to load - (libkern/kext) system policy prevents loading; check the system/kernel logs for errors or try kextutil(8).

Attachments

Installer Log 1-Oct-2018.txt Download (10.9 KB) - added by JasonMc 4 years ago.
Mojave Install failure VirtualBox-5.2.97-125396-OSX

Change History

Changed 4 years ago by JasonMc

Mojave Install failure VirtualBox-5.2.97-125396-OSX

comment:1 Changed 4 years ago by socratis

  1. 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. For example, yours is not a bug and someone from the developers has to deal with it and close it as "Invalid".
  1. This is an issue caused by Appple's increased security model, introduced with 10.13 beta. This is not a VirtualBox bug/issue, VirtualBox can't do anything about it. You need to read the following Apple KB article:  "User-Approved Kernel Extension Loading" and act upon it.
    1. If you do not see that "Allow" button, reboot the computer.
    2. If you are controlling your OSX remotely (RDP) the "Allow" button is clickable, but it does absolutely nothing. Another security-related decision by Apple.

comment:2 Changed 4 years ago by janitor

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

comment:3 follow-up: ↓ 4 Changed 4 years ago by JasonMc

Your team packages and ships the installer. So while not a bug with virtual box, it is a bug in something you track. It's an unfriendly error message. You can very simply on error pop your #2 comment and provide direction to resolve. That way preventing the need for further research into the issue.

The document even clearly states to look for the error 27 code, which should be handled by your postflight script.

If there is a component being tracked under the installer then I'd put it there as a improvement.

comment:4 in reply to: ↑ 3 ; follow-up: ↓ 5 Changed 4 years ago by socratis

Replying to JasonMc:

It's an unfriendly error message.

That's an Apple installer error message. You could/should talk to Apple about it.

You can very simply on error pop your #2 comment and provide direction to resolve. That way preventing the need for further research into the issue.

Again, that's an Apple installer error message. You could/should talk to Apple about it.

comment:5 in reply to: ↑ 4 Changed 3 years ago by TGOS

Replying to socratis:

Again, that's an Apple installer error message.

Which does not prevent your postflight script from displaying an own error message. So how is it Apple's fault that you are not displaying an appropriate error message?

You are linking to this page:

 https://developer.apple.com/library/archive/technotes/tn2459/_index.html

And this page says:

Starting with macOS High Sierra, installers and apps that load KEXTs should expect that KEXT loading will fail if the user hasn't approved their KEXT. Instead of treating this as an error, the user should be informed that they may need to approve the KEXT.

So why aren't you doing this? You are NOT informing the user and even though you shouldn't, you ARE treating this as an error and make the installer fail. This is NOT Apple's fault, this is is YOUR FAULT. You are basically not doing what Apple says that you should be doing. Apple's installer will work correctly if your postflight scripts works correctly but it doesn't. Why are you blaming Apple for you having an incorrect postflight script? How shall we talk with Apple about it? When we do, Apple says "Talk to the developer and make them fix their postflight script". So here we are and doing exactly that.

Last edited 3 years ago by TGOS (previous) (diff)

comment:6 Changed 3 years ago by ohumbel

  • Status changed from closed to reopened
  • Resolution invalid deleted

The installation of VirtualBox-5.2.30-130521-OSX.dmg fails on the new macOSX Mojave 10.14.5. Currently there is no workaround, meaning no way to allow the installation.

Others already have encountered this problem as well, see:

 https://eclecticlight.co/2019/05/13/mojave-10-14-5-changes-kernel-extension-security/

(Comment no. 7)

comment:7 Changed 3 years ago by bame

MacOS 10.14.5 VirtualBox 6.0.8 upgrading

May 17 16:26:48 demo installd[686]: PackageKit: Executing script "./postflight" in /private/tmp/PKInstallSandbox.aBLEiu/Scripts/org.virtualbox.pkg.vboxkexts.milQ3D

May 17 16:26:48 demo installd[686]: ./postflight: /Library/LaunchDaemons/org.virtualbox.startup.plist

May 17 16:26:49 demo installd[686]: ./postflight: /Library/Application Support/VirtualBox/VBoxDrv.kext failed to load - (libkern/kext) system policy prevents loading; check the system/kernel logs for errors or try kextutil(8).

...

May 17 16:26:51 demo Installer[8093]: Install failed: The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.

comment:9 Changed 3 years ago by michael

  • Status changed from reopened to closed
  • Resolution set to duplicate
  • Summary changed from Installation fails on new Mojave install MacOS 10.14 to Installation fails on new Mojave install MacOS 10.14 -> duplicate of #18645

Duplicate of #18645.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use