VM self-terminates on MacOS

[Ryan Lederman]

Note: I have only witnessed this behavior since upgrading to the last version I was prompted for.

Since upgrading to this version of VirtualBox, my VM disappears from the Dock, and its status is 'Aborted' in the VM manager window.

I am unable to identify any particular action taken by me that causes it, since I am never looking or using the VM when it happens.

---

MacOS: 10.13.6
VirtualBox: 5.2.16 r123759 (Qt5.6.3)
VM: Ubuntu 16.04 x64
Hardware: 2016 15" MBP, 2.9GHz, 16GB 2133MHz, Raedon Pro 460 4GB/Intel HD 530 1.5GB

---

I'm attaching the logs I saved through the GUI, and a cursory grep through /var/log/system.log yielded the following (I have no idea if it's related to the shutdown or not):

VirtualBox[26651]: objc[26651]: Class FIFinderSyncExtensionHost is implemented in
both /System/Library/PrivateFrameworks/FinderKit.framework/Versions/A/FinderKit (0x7fff8e04cc90)
and /System/Library/PrivateFrameworks/FileProvider.framework/OverrideBundles/FinderSyncCollaborationFileProviderOverride.bundle/Contents/MacOS/FinderSyncCollaborationFileProviderOverride (0x10dc79cd8).
One of the two will be used. Which one is undefined.
VirtualBox[26651]: notify name "user.uid.501.BRNotificationServerAvailabilityChanges"
has been registered 20 times - this may be a leak
VirtualBox[26651]: assertion failed: 17G65: libxpc.dylib + 75013
 [0BC7AD67-671D-31D4-8B88-C317B8379598]: 0x89

[Ryan Lederman]

Please email me if there are any other debugging steps you'd like me to take.

[Ryan Lederman]

updated logs

[Ryan Lederman]

This is still happening for me on 5.2.18 r124319 (Qt 5.6.3) on a different (created since upgrading) Ubuntu 18 x64 VM. Attaching new logs.

system log:

Sep 19 19:38:58 token VirtualBox[4617]: notify name "user.uid.501.BRNotificationServerAvailabilityChanges" has been registered 20 times - this may be a leak
Sep 19 19:38:58 token VirtualBox[4617]: assertion failed: 17G65: libxpc.dylib + 75013 [0BC7AD67-671D-31D4-8B88-C317B8379598]: 0x89

[aeichner]

Is there a crash report available from OS X you can upload?

[Ryan Lederman]

Replying to aeichner:

Is there a crash report available from OS X you can upload?

I found and attached a couple I think are relevant... please let me know if there's anything else I can do to help.

[Ryan Lederman]

I attached a couple more.

FYI: this seems to occur more often when I disconnect my external display from my MacBook Pro.

[aeichner]

Do you have any input devices connected to the external display which are disconnected when the display is disconnected?

[Ryan Lederman]

Replying to aeichner:

Do you have any input devices connected to the external display which are disconnected when the display is disconnected?

It didn’t occur to me but yes: there’s a USB keyboard attached to the display which is then attached to the laptop via USB-C.

[Ryan Lederman]

I've upgraded to 5.2.20 r125813 but it's still happening. This last time I was preparing to disconnect the laptop from my external monitor and decided to see if any USB devices were attached to the Ubuntu guest, in order to disassociate them before I disconnected the monitor, but when I went to Devices->USB->USB Settings, it crashed the VM.

Attaching relevant crash files.

[Ryan Lederman]

Adding another. FYI, this is a new MacBook Pro now, but I believe the issue remains the same. New hardware specs:

---

MacBook Pro (15-inch, 2018)
2.9 GHz Intel Core i9
32 GB 2400 MHz DDR4
Radeon Pro 560X 4096 MB
Intel UHD Graphics 630 1536 MB

---

USB 3.1 Bus:

Host Controller Driver: AppleIntelCNLUSBXHCI PCI Device ID: 0xa36d PCI Revision ID: 0x0010 PCI Vendor ID: 0x8086

USB 2.0 BILLBOARD :

Product ID: 0x0100 Vendor ID: 0x2109 (VIA Labs, Inc.) Version: 3.00 Serial Number: 0000000000000001 Speed: Up to 480 Mb/sec Manufacturer: VIA Technologies Inc. Location ID: 0x14400000 / 5 Current Available (mA): 500 Current Required (mA): 100 Extra Operating Current (mA): 0

Gadget:

Product ID: 0xa4a8 Vendor ID: 0x0525 (PLX Technology, Inc.) Version: 2.06 Serial Number: 0242920ca798 Speed: Up to 480 Mb/sec Manufacturer: Sparkage Location ID: 0x14200000 / 14 Current Available (mA): 500 Current Required (mA): 2 Extra Operating Current (mA): 0

Hub:

Product ID: 0x8142 Vendor ID: 0x0451 (Texas Instruments) Version: 1.00 Serial Number: 3E020071A6C5 Speed: Up to 480 Mb/sec Location ID: 0x14100000 / 15 Current Available (mA): 500 Current Required (mA): 0 Extra Operating Current (mA): 0

HID Keyboard:

Product ID: 0x0510 Vendor ID: 0x04b4 (Cypress Semiconductor) Version: 2.01 Speed: Up to 1.5 Mb/sec Manufacturer: HID Keyboard Location ID: 0x14130000 / 18 Current Available (mA): 500 Current Required (mA): 60 Extra Operating Current (mA): 0

TUSB3410 EECode Ser :

Product ID: 0x3410 Vendor ID: 0x0451 (Texas Instruments) Version: 1.01 Serial Number: 00262107 Speed: Up to 12 Mb/sec Manufacturer: Texas Instruments Location ID: 0x14140000 / 16 Current Available (mA): 500 Extra Operating Current (mA): 0

Texas Instruments USB Billboard Device:

Product ID: 0x3421 Vendor ID: 0x0451 (Texas Instruments) Version: 1.00 Serial Number: 66FF5CF9030A0428 Speed: Up to 12 Mb/sec Manufacturer: Texas Instruments Inc. Location ID: 0x14110000 / 17 Current Available (mA): 500 Current Required (mA): 100 Extra Operating Current (mA): 0

[Mikael Strom]

Log after crash and force quite

[Mikael Strom]

I have massive issues with USB as well. I have tried 5.2.18, 5.2.20 and 5.2.22 and all three crash my Arch Linux VM when working with Microchip ICD3 USB device.

MacOS: 10.12.6 (Sierra)
VirtualBox: 5.2.18, 5.2.20 and 5.2.22
VM: Arch Linux
Hardware: 2015 iMac

I have tried both the guest utils in Arch repos, as well as the one provided in VirtualBox installation, to no avail.

Typically, the ICD3 works when connected, and when used either have problems reading or writing from/to endpoints, or freeze the VM. When the VM freeze, i need to terminate VirtualBox as closing the VM (i.e. selecting power off) freeze VirtualBox (spinning ball), and the only way to do that is "Force quit" in MacOS.

Any suggestions are most welcome!

[Ryan Lederman]

Attaching another one. This time I was not (that I know of) unplugging or plugging in any devices.