Big Sur Host Issues

For discussions related to using VirtualBox on Mac OS X pre-releases

Big Sur Host Issues

Postby trifster » 24. Jun 2020, 13:10

Hi All,

While it will be macOS 11 (it was released as a developer beta as 10.16), macOS Big Sur seems to have some Kernel extension changes that i think will require Virtualbox fixes. Here is the error I get trying to launch my Ubuntu VM on 6.1.10.

Failed to open a session for the virtual machine Ubuntu Server.

The virtual machine 'Ubuntu Server' has terminated unexpectedly during startup with exit code 1 (0x1).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}

And

VERR_VM_DRIVER_OPEN_ERROR (rc=-1911)

Make sure the kernel module has been loaded successfully.

where: suplibOsInit what: 3 VERR_VM_DRIVER_OPEN_ERROR (-1911) - Was not able to open the support driver. Generic open error used when none of the other ones fit.


From the macOS 11 Big Sur Release Notes:
Kernel

New Features

The kern.argmax limit has been increased, allowing programs to receive longer argument lists. (48661669)

Darwin kevent now allows non-parent processes to register for NOTE_EXITSTATUS, which delivers the same values as the wait() family of functions in the event data. Refer to the wait4() man page for more information. This event is subject to the following security checks:

The requesting process is allowed to send signals by sandbox restrictions.

The requesting process and the target process are running as the same user or the requesting process has root privileges. (58134463)

Known Issues

Installing a new kernel extension requires signing in as an Admin user. During kernel extension development, every time a kernel extension is changed, it must be signed and notarized. In both cases, your Mac must be restarted to load the extension. (55068348)

Remote panic dumps aren't currently available. (57915324)

New in macOS Big Sur 11 beta, the system ships with a built-in dynamic linker cache of all system-provided libraries. As part of this change, copies of dynamic libraries are no longer present on the filesystem. Code that attempts to check for dynamic library presence by looking for a file at a path or enumerating a directory will fail. Instead, check for library presence by attempting to dlopen() the path, which will correctly check for the library in the cache. (62986286)

kmutil install might fail to build a development kextcache. (63772702)

Workaround: Copy the release .elides to the locations of the development .elides:


sudo cp /path/to/livemount/System/Library/KernelCollections/BootKernelExtensions.kc.elides /path/to/livemount/System/Library/KernelCollections/BootKernelExtensions.kc.development.elides
sudo cp /path/to/livemount/System/Library/KernelCollections/BootKernelExtensions.kc.elides /path/to/livemount/System/Library/KernelCollections/BootKernelExtensions.kc.kasan.elides
sudo cp /path/to/livemount/System/Library/KernelCollections/BootKernelExtensions.kc.elides /path/to/livemount/System/Library/KernelCollections/BootKernelExtensions.kc.debug.elides
sudo cp /path/to/livemount/System/Library/KernelCollections/SystemKernelExtensions.kc.elides /path/to/livemount/System/Library/KernelCollections/SystemKernelExtensions.kc.development.elides
sudo cp /path/to/livemount/System/Library/KernelCollections/SystemKernelExtensions.kc.elides /path/to/livemount/System/Library/KernelCollections/SystemKernelExtensions.kc.kasan.elides
sudo cp /path/to/livemount/System/Library/KernelCollections/SystemKernelExtensions.kc.elides /path/to/livemount/System/Library/KernelCollections/SystemKernelExtensions.kc.debug.elides
Use only absolute paths with the --volume-root option of kmutil, and don't use a trailing /. (63773848)

After removing a DriverKit extension, restart your Mac to complete uninstallation. (63995046)

Adhoc signed kernel extensions are displayed with a developer name of unknown in update dialogs and in Security preferences. (64215260)

Symbols exported by both xnu and Apple kernel extensions will change. Recompile your kernel extension with each update to macOS Big Sur 11 beta to ensure compatibility. (64262563)

Moving a kernel extension bundle out of /Library/Extensions might not completely uninstall it. (64331929)

Workaround:

Remove the extension from /Library/Extensions.

Boot to macOS Recovery.

Run Terminal.

Enter the command kmutil invoke-panic-medic.

Restart your Mac.

Follow the prompt to open System Preferences and navigate to Security & Privacy.

Follow the prompt to restart.

An unexpected System Extension Updated alert for third-party kernel extensions which are included in macOS might appear. These include: Accusys, Inc., ATTO Technology, Inc., Areca Technology Corporation, CalDigit, Inc., HighPoint Technologies, Inc., Promise Technology Mobile Apps, and Other World Computing. (64337113)

Deprecations

Kernel extensions using certain deprecated KPIs no longer load. Refer to the support page . While macOS Big Sur remains in development, you can temporarily disable System Integrity Protection to allow these deprecated extensions to load. (55068348)
trifster
 
Posts: 12
Joined: 16. Oct 2019, 01:54

Re: Big Sur Host Issues

Postby krays » 24. Jun 2020, 14:53

Similar problems here on macOS 11 - Big Sur - beta 1 (20A4299v).
I try to use following command in order to white list kernel extension in recovery mode, without success. (maybe I have wrong extID, not sur how to found full list of kernel ext ID)

Code: Select all   Expand viewCollapse view
spctl kext-consent add <extID>
krays
 
Posts: 1
Joined: 24. Jun 2020, 14:45

Re: Big Sur Host Issues

Postby trifster » 24. Jun 2020, 18:10

I’m thinking something in here.

110 0 0xffffff7f9efa6000 0xb1000 0xb1000 org.virtualbox.kext.VBoxDrv (6.1.10) 34EE0FE5-E591-300D-814B-D63D08217956 <8 6 5 3 1>

I’m going to uninstall VB, turn off SIP, reinstall and try again.
trifster
 
Posts: 12
Joined: 16. Oct 2019, 01:54

Re: Big Sur Host Issues

Postby trifster » 24. Jun 2020, 21:10

no go. install fails. from installer log

Jun 24 15:09:20 Trifs-iMac installd[1154]: PackageKit: Install Failed: Error Domain=PKInstallErrorDomain Code=112 "An error occurred while running scripts from the package “VirtualBox.pkg”." UserInfo={NSFilePath=./postflight, NSURL=file:///Volumes/VirtualBox/VirtualBox.pkg#VBoxKEXTs.pkg, PKInstallPackageIdentifier=org.virtualbox.pkg.vboxkexts, NSLocalizedDescription=An error occurred while running scripts from the package “VirtualBox.pkg”.} {
NSFilePath = "./postflight";
NSLocalizedDescription = "An error occurred while running scripts from the package \U201cVirtualBox.pkg\U201d.";
NSURL = "file:///Volumes/VirtualBox/VirtualBox.pkg#VBoxKEXTs.pkg";
PKInstallPackageIdentifier = "org.virtualbox.pkg.vboxkexts";
}
Jun 24 15:09:21 Trifs-iMac Installer[2793]: Install failed: The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.
Jun 24 15:09:21 Trifs-iMac Installer[2793]: IFDInstallController 323B060 state = 8
Jun 24 15:09:21 Trifs-iMac Installer[2793]: Displaying 'Install Failed' UI.
Jun 24 15:09:21 Trifs-iMac Installer[2793]: 'Install Failed' UI displayed message:'The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.'.
trifster
 
Posts: 12
Joined: 16. Oct 2019, 01:54

Re: Big Sur Host Issues

Postby PokeCaptain » 25. Jun 2020, 02:43

Not surprised VirtualBox's kexts are broken again. Last go around Apple specifically prevented the vbox kext from loading with their applekextexcludelist.kext. This does not seem to be the case this time, as Apple only seems to be blocking 6.0.4 and below.
Symbols exported by both xnu and Apple kernel extensions will change. Recompile your kernel extension with each update to macOS Big Sur 11 beta to ensure compatibility. (64262563)

This is the line to note. It's extremely unlikely Oracle will release a new recompiled version of the kext (and vbox as a whole) just to stay compatible with the latest version of a Mac developer beta. Don't expect a Big Sur release of VirtualBox until the GM.
PokeCaptain
 
Posts: 2
Joined: 19. Apr 2019, 04:52

Re: Big Sur Host Issues

Postby Pixelstart » 25. Jun 2020, 12:57

Hi all, of course a new MacOS release comes with issues like this. I'm trying to run Homestead and receiving the following error:

Code: Select all   Expand viewCollapse view
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["hostonlyif", "create"]

Stderr: 0%...
Progress state: NS_ERROR_FAILURE
VBoxManage: error: Failed to create the host-only adapter
VBoxManage: error: VBoxNetAdpCtl: Error while adding new interface: failed to open /dev/vboxnetctl: No such file or directory
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
VBoxManage: error: Context: "RTEXITCODE handleCreate(HandlerArg *)" at line 95 of file VBoxManageHostonly.cpp


Anyone who knows a workaround for this?
Pixelstart
 
Posts: 1
Joined: 25. Jun 2020, 12:54

Re: Big Sur Host Issues

Postby LordGnomish » 24. Jul 2020, 18:54

I installed CLT beta 3 version then installed latest version (6.1.13) of virtualbox. It worked for me
LordGnomish
 
Posts: 1
Joined: 24. Jul 2020, 18:44

Re: Big Sur Host Issues

Postby trifster » 25. Jul 2020, 14:23

LordGnomish wrote:I installed CLT beta 3 version then installed latest version (6.1.13) of virtualbox. It worked for me

Can you expand on this. CLT command line tools? Is that a VB feature or macOS? You got 6.1.13 to install on macOS 11 Big Sur dev beta 3?
trifster
 
Posts: 12
Joined: 16. Oct 2019, 01:54


Return to VirtualBox on Mac OS X pre-releases

Who is online

Users browsing this forum: No registered users and 2 guests