Virtualbox 6.1.14 Crashing on macOS Catalina (Windows 10 64 Guest)

[ddcvbo]

Hi, I know there are other threads about this but most of them seem to be locked.

I have tried a few recommendations posted but still happening every time I run vbox. Can't even get through the windows installation process.

May be tied to going between vbox window and other Mac apps, but not sure.

I can share any log files, settings files as needed, just let me know what might help!

Thanks much.

[ddcvbo]

Here is a log file attached. It's generated several so I wasn't sure which one was right. But hopefully this helps!

Thanks!

[mpack]

That log is truncated and does not include any indication of a crash. Always make sure the VM is closed down before copying files it had open for writing. If it's sitting there displaying an error dialog then the VM is still running. Also, zip the log before attaching the zip.

More information about the crash would be useful too: what exactly you were doing, and screenshot of the error message box.

[ddcvbo]

Thanks! I will try my best to oblige. Please see this log file attached - I quit VB and then grabbed the log.

As for a screen shots, I am just getting a MacOS message about the unexpected quit, and a status of 'Aborted' in the vbox window (both attached as well).

All the best.

[mpack]

Thanks for zipping the log this time, but otherwise it's practically identical: still truncated, no indication of any error. Are you sure that you closed the VM and not the manager - which is a separate program?

If the VM did simply abort without the exception handler catching it then that is very unusual, almost unheard of. One possibility is that the ISO you're using is bad. Hopefully it's an official ISO from Microsoft and you can simply download it again, and compare MD5 sums this time.

Other things: add a second vCPU to this VM (before installing Windows again). Windows 10 on one core is... unpleasant, and changing it later carries an activation strike. Also, install the extension pack on the host.

[granada29]

As for a screen shots, I am just getting a MacOS message about the unexpected quit, and a status of 'Aborted' in the vbox window (both attached as well).

I think the macOS crash dump is more useful than the VirtualBox log in this case. You should be able to find the crash dump file using /Applications/Utilities/Console.app

The crash dump will provide a back-trace showing what the VM was trying to do at the time of crash.

One thing you might try is to disable 3D acceleration in the guest Display settings. Also, re-verify that you have in fact disabled Audio.

[barrykn]

Unfortunately I'm doing this on a system that's using the dosdude1 patcher to run Mojave on a Mac that Apple only supports up to High Sierra (which is why I didn't post logs earlier), but since it seems like this is happening on supported Macs as well, hopefully my logs will still help.

[granada29]

The logs are showing that VirtualBox is still trying to open the audio driver, and due to a bug, this is failing and crashing.

Please verify that you have in fact disabled audio in the VM settings - like the screen in this image

[Daniel Horecki]

I have the same issue. Host MacOS Catalina, guests are Gentoo and FreeBSD. After disabling audio in settings I was able to boot systems, they will crash otherwise.
It was working in 6.1.12, so I guess it's regression.

[KodiakFiresmith]

+1, same versions of host OS and Vbox. Guest OS doesn't seem to matter, which makes sense if it's the host audio driver causing this. Guest OS is Ubuntu 20.04.

[interlated]

I can confirm that turning off audio runs the virtual machine.

[fansonly]

I can confirm that turning off audio runs the virtual machine.

Same. Audio off will boot. Guest Ubuntu 20.04

[gwillard]

I'm having the same problem but I'm on an iMac with a VB Version 6.1.14 r140239 (Qt5.6.3 and with a Linux OS Guess 6.x, with the following info below, and the workaround like starting the VB from iMac term and starting the guess OS VM also crashes And the fact this problem has been around since March concerns me as I use the VM in all me Exadata Installs and there has been no progress is not a good thing.

Process: VirtualBoxVM [2749]
Path: /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM
Identifier: org.virtualbox.app.VirtualBoxVM
Version: 6.1.14 (6.1.14)
Code Type: X86-64 (Native)
Parent Process: VBoxSVC [2746]
Responsible: VirtualBox [2742]
User ID: 501

Date/Time: 2020-09-26 01:14:55.086 -0400
OS Version: Mac OS X 10.15.7 (19H2)
Report Version: 12
Bridge OS Version: 4.6 (17P6610)
Anonymous UUID: 332BCB24-4F91-6B8F-551F-F1118C54A7AA


Time Awake Since Boot: 5400 seconds

System Integrity Protection: enabled

Crashed Thread: 10 Dispatch queue: com.apple.root.default-qos

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

Termination Reason: Namespace TCC, Code 0x0

[gerryvz]

I can confirm (iMac 2019 27"), with Windows XP guest OS, that if you turn off the audio in the VM settings, it will allow things to load correctly. This seemed to just crop up with the latest patch of MacOS Catalina (10.15.7), which I installed yesterday. Things were working fine before I installed that patch.

BTW, VirttualBox is NOT working (or was not) with the early public betas of MacOS Big Sur. I don't know if that has been solved yet or not.

[Castle650]

All the above happening to me as well.

VB version 6.1.14 r140239 (Qt5.6.3)

Client is: Windows XP pro - genuine disk and key. Same issue with a windows XP home install - again genuine.
Host is OSX Catalina

If audio enabled with CoreAudio and ICH AC97 then the VB logs cease at this point "CoreAudio: macOS 10.14+ detected, checking audio input permissions". Nothing after this in the VB logs.

If audio is disabled the machine starts.
If audio enabled but the "Null Audio Driver" is selected then the machine loads but the VB logs show no attempt to access CoreAudio so this is not surprising.

Many logs of VirtualBoxVM crash dumps. One of VirtualBox itself. One of CoreAudio.

The CoreAudio crash dump brings up:
Application Specific Information:
dyld3 mode
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[__NSDictionaryM __setObject:forKey:]: key cannot be nil'
terminating with uncaught exception of type NSException
abort() called

This appears to relate to other posts I have seen in the search for answers for this - that VB config is not setting up CoreAudio properly - something about 250msec now and 100msec is required - but these posts dated back to VB release 5.

Crashdumps from OSX attached.
Logs from VB attached

Edit zip remove - I need to make it more annonymous
Edit zip added back

Update. Reverted to VirtualBox 6.1.12 (core, extensions and client extensions) and all good - I have audio now.