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: 17
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: 17
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: 17
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: 17
Joined: 16. Oct 2019, 01:54

Re: Big Sur Host Issues

Postby jbeckman » 10. Aug 2020, 01:49

I tried starting a VM with Big Sur Beta 4 and VirtualBox 6.1.13 (latest dev build) to no avail. I am getting the same issues reported in this thread.
jbeckman
 
Posts: 1
Joined: 10. Aug 2020, 01:46

Re: Big Sur Host Issues

Postby trifster » 12. Aug 2020, 16:52

jbeckman wrote:I tried starting a VM with Big Sur Beta 4 and VirtualBox 6.1.13 (latest dev build) to no avail. I am getting the same issues reported in this thread.


Parallels 16 (just released) works on Big Sur Beta 4 (SIP disabled). I couldn't get the convert/import to work selecting the .vbox file but it did recognize the .vdi. I'm going to wait until beta 5 before I make any final conclusions. Apple dorked up sandboxing/kext on 10.15.6 also (see main Mac OS X Hosts) with a kernel memory leak. Such a mess.
trifster
 
Posts: 17
Joined: 16. Oct 2019, 01:54

Re: Big Sur Host Issues

Postby iFred » 13. Aug 2020, 06:23

I'm in the same situation where I ran the installer, jumped through the hoops with permissions, and the install fails. The package is still setup, and you can event config VMs, but the moment the kernel extension is called, it crashes.

Code: Select all   Expand viewCollapse view
2020-08-12 20:54:20-07 MacBook-Pro package_script_service[717]: ./postflight: /Library/LaunchDaemons/org.virtualbox.startup.plist
2020-08-12 20:54:20-07 MacBook-Pro package_script_service[717]: ./postflight: Executing: /usr/bin/kmutil unload -b org.virtualbox.kext.VBoxDrv
2020-08-12 20:54:20-07 MacBook-Pro package_script_service[717]: ./postflight: Executing: /usr/bin/kmutil load -p /Library/Application Support/VirtualBox/VBoxDrv.kext
2020-08-12 20:54:22-07 MacBook-Pro package_script_service[717]: ./postflight: Error: Error Domain=KMErrorDomain Code=1 "Kernel request failed: (libkern/kext) kext (kmod) start/stop routine failed
2020-08-12 20:54:22-07 MacBook-Pro package_script_service[717]: ./postflight: Kernel request failed: (libkern/kext) dependency load failed
2020-08-12 20:54:22-07 MacBook-Pro package_script_service[717]: ./postflight: Kernel request failed: (libkern/kext) dependency load failed
2020-08-12 20:54:22-07 MacBook-Pro package_script_service[717]: ./postflight: Kernel request failed: (libkern/kext) dependency load failed" UserInfo={NSLocalizedDescription=Kernel request failed: (libkern/kext) kext (kmod) start/stop routine failed
2020-08-12 20:54:22-07 MacBook-Pro package_script_service[717]: ./postflight: Kernel request failed: (libkern/kext) dependency load failed
2020-08-12 20:54:22-07 MacBook-Pro package_script_service[717]: ./postflight: Kernel request failed: (libkern/kext) dependency load failed
2020-08-12 20:54:22-07 MacBook-Pro package_script_service[717]: ./postflight: Kernel request failed: (libkern/kext) dependency load failed}


...and here are the failures when you try to reload the extension, which is what I am assuming is failing in the validation script.

Code: Select all   Expand viewCollapse view
person@MacBookPro ~ % sudo "/Library/Application Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh" restart
Password:
Unloading VBoxDrv.kext
Executing: /usr/bin/kmutil unload -b org.virtualbox.kext.VBoxDrv
Loading VBoxDrv.kext
Executing: /usr/bin/kmutil load -p /Library/Application Support/VirtualBox/VBoxDrv.kext
Error: Error Domain=KMErrorDomain Code=1 "Kernel request failed: (libkern/kext) kext (kmod) start/stop routine failed
Kernel request failed: (libkern/kext) dependency load failed
Kernel request failed: (libkern/kext) dependency load failed
Kernel request failed: (libkern/kext) dependency load failed" UserInfo={NSLocalizedDescription=Kernel request failed: (libkern/kext) kext (kmod) start/stop routine failed
Kernel request failed: (libkern/kext) dependency load failed
Kernel request failed: (libkern/kext) dependency load failed
Kernel request failed: (libkern/kext) dependency load failed}
Error: Failed to load /Library/Application Support/VirtualBox/VBoxDrv.kext
Loading VBoxUSB.kext
Executing: /usr/bin/kmutil load -p /Library/Application Support/VirtualBox/VBoxUSB.kext -p /Library/Application Support/VirtualBox/VBoxDrv.kext
Error: Error Domain=KMErrorDomain Code=1 "Kernel request failed: (libkern/kext) dependency load failed
Kernel request failed: (libkern/kext) kext (kmod) start/stop routine failed
Kernel request failed: (libkern/kext) dependency load failed
Kernel request failed: (libkern/kext) dependency load failed" UserInfo={NSLocalizedDescription=Kernel request failed: (libkern/kext) dependency load failed
Kernel request failed: (libkern/kext) kext (kmod) start/stop routine failed
Kernel request failed: (libkern/kext) dependency load failed
Kernel request failed: (libkern/kext) dependency load failed}
Error: Failed to load /Library/Application Support/VirtualBox/VBoxUSB.kext
Loading VBoxNetFlt.kext
Executing: /usr/bin/kmutil load -p /Library/Application Support/VirtualBox/VBoxNetFlt.kext -p /Library/Application Support/VirtualBox/VBoxDrv.kext
Error: Error Domain=KMErrorDomain Code=1 "Kernel request failed: (libkern/kext) dependency load failed
Kernel request failed: (libkern/kext) kext (kmod) start/stop routine failed
Kernel request failed: (libkern/kext) dependency load failed
Kernel request failed: (libkern/kext) dependency load failed" UserInfo={NSLocalizedDescription=Kernel request failed: (libkern/kext) dependency load failed
Kernel request failed: (libkern/kext) kext (kmod) start/stop routine failed
Kernel request failed: (libkern/kext) dependency load failed
Kernel request failed: (libkern/kext) dependency load failed}
Error: Failed to load /Library/Application Support/VirtualBox/VBoxNetFlt.kext
Loading VBoxNetAdp.kext
Executing: /usr/bin/kmutil load -p /Library/Application Support/VirtualBox/VBoxNetAdp.kext -p /Library/Application Support/VirtualBox/VBoxDrv.kext
Error: Error Domain=KMErrorDomain Code=1 "Kernel request failed: (libkern/kext) dependency load failed
Kernel request failed: (libkern/kext) dependency load failed
Kernel request failed: (libkern/kext) dependency load failed
Kernel request failed: (libkern/kext) kext (kmod) start/stop routine failed" UserInfo={NSLocalizedDescription=Kernel request failed: (libkern/kext) dependency load failed
Kernel request failed: (libkern/kext) dependency load failed
Kernel request failed: (libkern/kext) dependency load failed
Kernel request failed: (libkern/kext) kext (kmod) start/stop routine failed}
Error: Failed to load /Library/Application Support/VirtualBox/VBoxNetAdp.kext
Executing: /usr/bin/kmutil unload -b org.virtualbox.kext.VBoxNetAdp
Executing: /usr/bin/kmutil unload -b org.virtualbox.kext.VBoxNetFlt
Executing: /usr/bin/kmutil unload -b org.virtualbox.kext.VBoxUSB
Executing: /usr/bin/kmutil unload -b org.virtualbox.kext.VBoxDrv
Error: Kernel request failed: (libkern/kext) kext is in use or retained (cannot unload)
Fatal error: VirtualBox
iFred
 
Posts: 1
Joined: 13. Aug 2020, 06:16

Re: Big Sur Host Issues

Postby acmdorio » 24. Aug 2020, 13:52

Hi all !!!

Hoping it helps, I've got the VB Version 6.1.12 r139181 (Qt5.6.3) installed on BS 11.0 Beta (20A5354i) by Homebrew (I guess download from Oracle and manually install works as well).

Sadly, any VM runs... returning an error showing the driver is not installed. Maybe Oracle should test if the host OS supports the new version of VB before installing it and shows a warning, just in case.

-------
BoxManage: error: The virtual machine X has terminated unexpectedly during startup with exit code 1 (0x1)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine

Kernel Driver not installed (rc=-1908). (...). The support driver is not installed. (...)
-------

VirtualBox VM report:

-------
Process: VirtualBoxVM [8356]
Path: /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM
Identifier: org.virtualbox.app.VirtualBoxVM
Version: 6.1.12 (6.1.12)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: VirtualBox [8272]
User ID: 501

Date/Time: 2020-08-24 13:41:19.872 +0200
OS Version: Mac OS X 10.16 (20A5354i)
Report Version: 12
Bridge OS Version: 3.0 (14Y908)
Anonymous UUID: 397C9717-E605-72D2-7A9D-059C9D6441E1

Sleep/Wake UUID: B2F728A1-5D1C-4A08-A957-4FC9952165EF

Time Awake Since Boot: 44000 seconds
Time Since Wake: 8700 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Application Specific Information:
crashed on child side of fork pre-exec

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff6a709552 __pthread_kill + 10
1 libsystem_pthread.dylib 0x00007fff6a7d0671 pthread_kill + 263
2 libsystem_c.dylib 0x00007fff6a67c740 abort + 120
3 org.qt-project.QtCoreVBox 0x00000001075a8619 0x107592000 + 91673
4 org.qt-project.QtCoreVBox 0x00000001075aa020 QMessageLogger::fatal(char const*, ...) const + 224
5 VirtualBoxVM.dylib 0x00000001073fab7b TrustedError + 1691
6 org.virtualbox.app.VirtualBoxVM 0x00000001073acd70 0x1073aa000 + 11632
7 org.virtualbox.app.VirtualBoxVM 0x00000001073acf1d 0x1073aa000 + 12061
8 org.virtualbox.app.VirtualBoxVM 0x00000001073ad3a6 0x1073aa000 + 13222
9 org.virtualbox.app.VirtualBoxVM 0x00000001073ad4bd 0x1073aa000 + 13501
10 libdyld.dylib 0x00007fff6a594851 start + 1

Thread 1:
0 libsystem_pthread.dylib 0x00007fff6a7cc4b4 start_wqthread + 0

Thread 2:
0 libsystem_pthread.dylib 0x00007fff6a7cc4b4 start_wqthread + 0

Thread 3:
0 libsystem_pthread.dylib 0x00007fff6a7cc4b4 start_wqthread + 0

Thread 4:
0 libsystem_pthread.dylib 0x00007fff6a7cc4b4 start_wqthread + 0

Thread 5:
0 libsystem_pthread.dylib 0x00007fff6a7cc4b4 start_wqthread + 0

Thread 6:: com.apple.NSEventThread
0 libsystem_kernel.dylib 0x00007fff6a702f6e mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff6a7032e0 mach_msg + 60
2 com.apple.CoreFoundation 0x00007fff28b9a72a __CFRunLoopServiceMachPort + 316
3 com.apple.CoreFoundation 0x00007fff28b98e0a __CFRunLoopRun + 1315
4 com.apple.CoreFoundation 0x00007fff28b981fe CFRunLoopRunSpecific + 563
5 com.apple.AppKit 0x00007fff25aee26a _NSEventThread + 124
6 libsystem_pthread.dylib 0x00007fff6a7d09b4 _pthread_start + 224
7 libsystem_pthread.dylib 0x00007fff6a7cc4d7 thread_start + 15

Thread 7:
0 libsystem_pthread.dylib 0x00007fff6a7cc4b4 start_wqthread + 0

Thread 8:
0 libsystem_pthread.dylib 0x00007fff6a7cc4b4 start_wqthread + 0

Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x00000001105bde00 rcx: 0x00007ffee884e908 rdx: 0x0000000000000000
rdi: 0x0000000000000303 rsi: 0x0000000000000006 rbp: 0x00007ffee884e930 rsp: 0x00007ffee884e908
r8: 0x00000000000130a8 r9: 0x00007fff8e31df98 r10: 0x00000001105bde00 r11: 0x0000000000000246
r12: 0x0000000000000303 r13: 0x0000000000000003 r14: 0x0000000000000006 r15: 0x0000000000000016
rip: 0x00007fff6a709552 rfl: 0x0000000000000246 cr2: 0x00007fd57431a000

Logical CPU: 0
Error Code: 0x02000170
Trap Number: 133
acmdorio
 
Posts: 1
Joined: 24. Aug 2020, 12:58

Re: Big Sur Host Issues

Postby vlados » 31. Aug 2020, 00:00

Any updates?
vlados
 
Posts: 2
Joined: 31. Aug 2020, 00:00

Re: Big Sur Host Issues

Postby estamos » 31. Aug 2020, 09:38

At the moment, is there any chance to have a fully working VM ?

- macOS Big Sur v11.0 Beta (20A5354i)
- VirtualBox 6.1.13 r140123 (Qt5.6.3)
- Command Line Tools for Xcode 12 beta 5
estamos
 
Posts: 3
Joined: 31. Aug 2020, 09:34

Re: Big Sur Host Issues

Postby vlados » 31. Aug 2020, 10:41

estamos wrote:At the moment, is there any chance to have a fully working VM ?

- macOS Big Sur v11.0 Beta (20A5354i)
- VirtualBox 6.1.13 r140123 (Qt5.6.3)
- Command Line Tools for Xcode 12 beta 5


I am with the same specifications, VirtualBox installed successful, but cannot start virtual machine
vlados
 
Posts: 2
Joined: 31. Aug 2020, 00:00

Next

Return to VirtualBox on Mac OS X pre-releases

Who is online

Users browsing this forum: No registered users and 2 guests