VirtualBox crashes after upgrading to macOS Catalina (#18990)

[socratis]

Not sure if that's another manifestation of the same problem or just yet another problem.

Another problem.

[socratis]

Mind if I asked.

Yes, I will mind. Don't polute the thread with seemingly unrelated issues, don't throw everything into one thread. This is a very specific thread, with a very specific issue, with very specific resolutions. Let's keep it like that...

[socratis]

westfalia,
I merged your question with the thread that deals with the issue. Read it from the beginning please...

[yashs20]

Another thing to try is to enter the command:

VBoxManage setextradata global GUI/HidLedsSync 0

Worked. Thank you so much!

[sinclaw]

VBoxManage setextradata global GUI/HidLedsSync 0

Worked for me as well on MacOS 10.15 running Virtualbox Version 6.0.12 r133076 (Qt5.6.3) and VM running Centos (Cloudera Hortonworks HDP Sandbox).

[Kaplan]

Another thing to try is to enter the command:

VBoxManage setextradata global GUI/HidLedsSync 0

Worked beautifully. Thanks a lot!

[alteh]

Hi,

I've upgraded my Mac Mini (Late 2012) to macOS 10.15 Catalina, and now my Windows 10 guest VM crashes every time I change focus outside of the guest window.

Does anybody else have this problem? Is it a Mac issue, Windows issue, or VirtualBox issue?

I attach the crash report.

Thanks.

[AntonioRibeiro]

VBoxManage setextradata global GUI/HidLedsSync 0

Fixed it for me. Thank you!

[socratis]

Does anybody else have this problem? Is it a Mac issue, Windows issue, or VirtualBox issue?

Yes, plenty of people. It's an old bug that got into prominence with 10.15. Read the thread that I merged your post with from the beginning...

BTW, your post didn't belong in the "OSX Guests" area. Either in the "Windows Guests", or in the "OSX Hosts" area.

[marvin42]

Another thing to try is to enter the command:

VBoxManage setextradata global GUI/HidLedsSync 0

Please, I need help on this: My VM Box crashes a lot of times, too. So I try this command, but now VMBox will not longer start. What can I do? What is the command, to cancel this command?

[socratis]

What is the command, to cancel this command?

The answer has already been posted, please read the thread carefully, no need to repeat what's already been said...

[Antartic0]

Pfff... I solved my problem with the command "csrutil disable" in Recovery mode and the beta version from Virtualbox repository. The other command doesn`t work for me.
And one more thing: When I reactivate the SIP the VM doesn`t start... curious.

I´m waiting for the last release.

Macbook Pro 2017 Retina Display
MacOS Catalina 10.15
Virtualbox 6.0.13 rt133800(Qt5.6.3)

Salu2.

[Desert36]

Hi all,

I had the same issues and crashes, but i was able to start my virtual machines with option: DETACHABLE when start the VM.

[fc57]

It works for me with terminal command "VBoxManage setextradata global GUI/HidLedsSync 0". Running on a MacBook Air 2017

[baz123]

I am running Ubuntu on a Mac OS host machine. Whenever I switch to another desktop or the laptop goes to sleep, the linux aborts. The first lines of the log file are:

Code: Select all   Expand viewCollapse view

Process:               VirtualBoxVM [9243]
Path:                  /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM
Identifier:            org.virtualbox.app.VirtualBoxVM
Version:               6.0.12 (6.0.12)
Code Type:             X86-64 (Native)
Parent Process:        VBoxSVC [2547]
User ID:               501

Date/Time:             2019-10-15 21:24:12.829 +0100
OS Version:            Mac OS X 10.15 (19A583)
Report Version:        12
Anonymous UUID:        F1484E0C-B258-752F-B6FA-4197DFF3B9E4

Sleep/Wake UUID:       41DBDDDB-552B-496C-9B9F-60D434BA4037

Time Awake Since Boot: 82000 seconds
Time Since Wake:       6100 seconds

System Integrity Protection: enabled

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

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x000007fc04d55e68
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Segmentation fault: 11
Termination Reason:    Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [9243]