virtualbox.org

The latest magic keyboard is a complete sealed unit with no way of removing the battery (short of destroying the whole thing). I have no idea how long the remaining 20% charge will last. Several weeks probably!

-Andy.

Thanks for trying, Andy. I just tried again to provoke the panic, and I was successful. The panic occurred, same as always. I've also reproduced this on two different host machines, and on VirtualBox 5.2.26 and 6.0.4. Both machines were running Mac OS 10.14.3, though. I'll also point out that I'm using the older apple bluetooth peripherals, which take AA batteries that you insert by unscrewing a cap on the left side.

Here's another ticket on this same issue: https://www.virtualbox.org/ticket/18360. Apparently this person "solved" it by disabling bluetooth altogether, but I have no other non-bluetooth peripherals, so this won't work for me.

I've seen other mentions in the forum of this same message I get in the panic report, but the other mentions are not necessarily associated with bluetooth:

"invalid commandSleep while not holding the gate"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-4903.241.1/iokit/Kernel/IOCommandGate.cpp:303

Does this give anyone any hints?

OK, let's try and find the common denominator. I think it would be wise to summarize the hardware/software combinations, both from those affected and those that are not (I'm looking at you Andy ). I'm going to be using the data from the crash report of 'acs87':

1. Model Identifier: iMac15,1 (as can be seen in the System Information)
2. OSX version: 10.14.3
3. VirtualBox version(s): 5.2.26 and 6.0.4
4. Keyboard model/type: keyboard model A1314
5. Mouse model/type: trackpad model A1339
6. Bluetooth: Version 6.0.10f1, 3 services, 27 devices, 1 incoming serial ports
7. List of Bluetooth loaded kexts:
   • com.apple.driver.AppleBluetoothMultitouch (96)
   • com.apple.iokit.IOBluetoothSerialManager (6.0.10f1)
   • com.apple.iokit.IOBluetoothUSBDFU (6.0.10f1)
   • com.apple.driver.AppleBluetoothHIDKeyboard (208)
   • com.apple.driver.IOBluetoothHIDDriver (6.0.10f1)
   • com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport (6.0.10f1)
   • com.apple.iokit.IOBluetoothHostControllerUSBTransport (6.0.10f1)
   • com.apple.iokit.IOBluetoothHostControllerTransport (6.0.10f1)
   • com.apple.iokit.IOBluetoothFamily (6.0.10f1)

Because I have a feeling (well, technically _not_ me, but a developer) that Apple might not be using the same driver for different BT keyboards.

Edit: Updated keyboard/trackpad info based on the next post by 'acs87'

To add to socratis' post: keyboard model A1314, trackpad model A1339. I have two of each, one set for my iMac15,1, and another set for my MacBookPro14,3. I'll reproduce the kernel panic on my MacBookPro14,3 when I get home tonight, and post the report, but I can say already that the bluetooth version is also 6.0.10f1, and the Mac OS version is the same.

Here are the statistics (vital or otherwise) from my iMac:

1. Model Identifier: iMac18,3 (2017 iMac 5K)
2. OSX version: 10.14.2
3. VirtualBox version(s): 6.0.4
4. Keyboard model/type: Magic Keyboard (model A1644)
5. Mouse model/type: Magic Mouse 2 (model A1657)
6. Bluetooth: Version 6.0.9f2
7. List of Bluetooth loaded kexts:
   • com.apple.iokit.IOBluetoothFamily (6.0.9f2)
   • com.apple.iokit.IOBluetoothHostControllerTransport (6.0.9f2)
   • com.apple.iokit.IOBluetoothHostControllerUSBTransport (6.0.9f2)
   • com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport (6.0.9f2)
   • com.apple.iokit.BroadcomBluetooth20703USBTransport (6.0.9f2)
   • com.apple.iokit.IOBluetoothSerialManager (6.0.9f2)
   • com.apple.driver.IOBluetoothHIDDriver (6.0.9f2)
   • com.apple.driver.AppleHSBluetoothDriver (138.2)

-Andy.

acs87 wrote:Thank you, Andy! Just a helpful hint: the kernel panic seems to occur not on the disconnect, but on the reconnect.

I've been told by a client that the guest window has to be the active one, but I can't test it myself. Maybe someone can check that out?

wndkk wrote:I've been told by a client that the guest window has to be the active one, but I can't test it myself. Maybe someone can check that out?

That is correct, it only occurs if the guest is the active window.

Here are the vital details from my MacBook Pro 15" 2017:

1. Model Identifier: MacBookPro14,3 (as can be seen in the System Information)
2. OSX version: 10.14.3
3. VirtualBox version(s): 5.2.26 and 6.0.4
4. Keyboard model/type: keyboard model A1314
5. Mouse model/type: trackpad model A1339
6. Bluetooth: Version 6.0.10f1, 3 services, 27 devices, 1 incoming serial ports
7. List of Bluetooth loaded kexts:
   • com.apple.driver.AppleBluetoothMultitouch (96)
   • com.apple.iokit.IOBluetoothSerialManager (6.0.10f1)
   • com.apple.driver.AppleBluetoothHIDKeyboard (208)
   • com.apple.iokit.IOBluetoothHostControllerUARTTransport (6.0.10f1)
   • com.apple.iokit.IOBluetoothHostControllerTransport (6.0.10f1)
   • com.apple.driver.AppleHSBluetoothDriver (138.2)
   • com.apple.driver.IOBluetoothHIDDriver (6.0.10f1)
   • com.apple.iokit.IOBluetoothFamily (6.0.10f1)

I've also edited my original post to put the report from my MacBook Pro right below the report from my iMac.

Does this only happen with Windows as a guest or do some of you use another OS?

Here's my config, I don't get crashes:

1. Model Identifier: Mac13,2
2. OSX version: 10.14.3
3. VirtualBox version(s): 6.0.4
4. Keyboard model/type: A1644
5. Mouse model/type: Logitech M720
6. Bluetooth: 6.0.10f1
7. List of Bluetooth loaded kexts:
   • com.apple.iokit.IOBluetoothFamily (6.0.10f1)
   • com.apple.driver.IOBluetoothHIDDriver (6.0.10f1)
   • com.apple.driver.AppleHSBluetoothDriver (138.2)
   • com.apple.iokit.IOBluetoothHostControllerTransport (6.0.10f1)
   • com.apple.iokit.IOBluetoothHostControllerUSBTransport (6.0.10f1)
   • com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport (6.0.10f1)
   • com.apple.iokit.IOBluetoothSerialManager (6.0.10f1)

wndkk wrote:I don't get crashes:

What do you mean you "don't get crashes"?
You have already 3 posts in this thread that talk about a crash!

It's not my computer thats crashing, it's that of a client.

Then post the information about your client!

Would do that if I had it
I'll have to check next time I'm able to.

wndkk wrote:Does this only happen with Windows as a guest or do some of you use another OS?

It happens with any guest OS. I've tested with WinXP, Win7, Ubuntu, and Debian.

OK, finally made the time to update to 10.14.3. I have repeated the tests that I ran in my previous post and still no kernel panic. Here is the updated information...

1. Model Identifier: iMac18,3 (2017 iMac 5K)
2. OSX version: 10.14.3
3. VirtualBox version(s): 6.0.4
4. Keyboard model/type: Magic Keyboard (model A1644)
5. Mouse model/type: Magic Mouse 2 (model A1657)
6. Bluetooth: Version 6.0.10f1
7. List of Bluetooth loaded kexts:
   • com.apple.iokit.IOBluetoothFamily (6.0.10f1)
   • com.apple.iokit.IOBluetoothSerialManager (6.0.10f1)
   • com.apple.iokit.IOBluetoothHostControllerTransport (6.0.10f1)
   • com.apple.iokit.IOBluetoothHostControllerUSBTransport (6.0.10f1)
   • com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport (6.0.10f1)
   • com.apple.iokit.BroadcomBluetooth20703USBTransport (6.0.10f1)
   • com.apple.driver.IOBluetoothHIDDriver (6.0.10f1)
   • com.apple.driver.AppleHSBluetoothDriver (138.2)

-Andy

Hi,

I can add my voice to the "getting panic" list. Same keyboard and touchpad as the OP.

Her is my typical senario for the when it happens:
- Getting back to work and resuming the Mac from sleep.
- I have the same keyboard and trackpad but I don't touch them (yet!)
- Connecting external monitors
- Start VirtualBox Win10 client while using the built-in keyboard and mouse
- The client opens full-screen in one of the external screens
- Moving cursor over using internal trackpad
- Swiping away the full-screen client using EXTERNAL touchpad
- PANIC

So, I guess the touchpad was still sleeping at this point and waking up by the swipe and then this triggers the panic.
I have also gotten this at other points without having a complete picture as how and when but I suspect it it getting back from lunch or a meeting and the BT decice having gone to sleep again.

Until this is fixed I will make sure I have used the external devices in the host before starting any clients.