Repeated Hard Crashes on MacOS High Sierra

[SaulH]

Is com.apple.driver.AppleMikeyHIDDriver always the last loaded/unloaded kext? If yes, it's probably relevant.

I've been trying to keep an eye on that, and it is often the last loaded/unloaded kext, but not always.

[SaulH]

@SaulH
Do you get a crash if you don't run it with VBoxHeadless, i.e. normal start from VirtualBox Manager?

@socratis

I've been running with the normal VirtualBox manager since I posted (after noticing that VBoxHeadless seemed to appear in many of these logs), and haven't had any panics, yet! This is a big improvement from the ~4 panics/day I was seeing while using VBoxHeadless.

[socratis]

I've been running with the normal VirtualBox manager ... and haven't had any panics, yet!

Just to make 100% sure SaulH, running VirtualBox Manager and selecting the drop-down arrow next to the big green right arrow (that typically starts a VM normally), and choosing "Headless Start" doesn't crash your OSX, right?

While starting the VM with the "VBoxHeadless" command line, does.

PS. The same type of start can be achieved by right-clicking on the VM » Start... » Headless Start.

[SaulH]

When I was getting frequent panics, I was starting VBoxHeadless by right-clicking on the VM, not from the command line.

[socratis]

Can you please try the command-line VBoxHeadless option? I know I'm asking you to put your host into a potential kernel panic mode, but I wish I knew of another way to trigger this. What happens if you start your VM with either of these two commands?

VBoxManage startvm "<Your_VM>" --type headless

VBoxHeadless --startvm "<Your_VM>"

And please fill in the following questionnaire, because I'm getting a little confused (not enough caffeine). When starting the VM as follows, I get a kernel panic:

1. Command-line VBoxHeadles: Yes/No
2. Command-line VBoxManage: Yes/No
3. Right-click, start headless: Yes/No
4. Click the drop-down arrow on the Start icon: Yes/No

[foo_]

My Mac crashed again when I was a running a Windows 10 guest under load and some other VMs. Should I post the crash dump of my Mac or the VM logs or both?

[socratis]

@foo_
Start by posting the output of the command:

kextstat | grep -v com.apple

[socratis]

kextstat | grep -v com.apple
Index Refs Address            Size       Wired      Name (Version) UUID <Linked Against>
  106    1 0xffffff7f80e42000 0x45000    0x45000    com.Logitech.Control Center.HID Driver (3.9.5) no UUID <105 82 50 45 5 4 3>
  116    0 0xffffff7f80e97000 0x17000    0x17000    com.Logitech.Unifying.HID Driver (1.3.5) no UUID <106 105 50 45 5 4 3>
  165    0 0xffffff7f81336000 0x4000     0x4000     com.protech.NoSleep (1.4.0) 79207772-D7BF-34EE-B7B6-6E90A96D8062 <5 4 3>
  166    0 0xffffff7f8109c000 0x62000    0x62000    com.paragon-software.kext.VDMounter (4.2) 3F301F93-CB8D-3149-8C74-D68B3D1C6D52 <25 5 4 3 1>
  178    3 0xffffff7f85e21000 0x64000    0x64000    org.virtualbox.kext.VBoxDrv (5.2.12) 3AABEB96-18B4-378E-B3EE-A0F6EB91DDE7 <7 5 4 3 1>
  183    0 0xffffff7f85e85000 0x8000     0x8000     org.virtualbox.kext.VBoxUSB (5.2.12) 9ABE1230-E87E-3B89-8E2A-B0B3BAA5F63D <182 178 50 7 5 4 3 1>
  184    0 0xffffff7f85e8d000 0x5000     0x5000     org.virtualbox.kext.VBoxNetFlt (5.2.12) 3EF145FE-B581-3F71-8F0F-E04C62C5A91D <178 7 5 4 3 1>
  185    0 0xffffff7f85e92000 0x6000     0x6000     org.virtualbox.kext.VBoxNetAdp (5.2.12) F6F0D614-6816-3226-9263-DA96DB33D890 <178 5 4 1>

[socratis]

com.Logitech.Control Center.HID Driver (3.9.5)
com.Logitech.Unifying.HID Driver (1.3.5)
com.protech.NoSleep (1.4.0)

Uninstall first the Logitech software and then the ProTech software. See if that changes the situation...

[ijaureguialzo]

I have experienced a crash like the ones described here. I was running two machines in headless mode, both started by vagrant, and they crashed when the boxes where being imported, so heavy disk usage was underway. One is a CentOS and the other a Ubuntu, both command line only.

Loaded extensions:

Code: Select all   Expand viewCollapse view

Index Refs Address            Size       Wired      Name (Version) UUID <Linked Against>
   85    0 0xffffff7f80d54000 0x17c000   0x17c000   at.obdev.nke.LittleSnitch (5124) BDAB2F2E-B581-37EB-AE29-BE8F2DD56D5C <7 5 4 3 1>
  152    0 0xffffff7f80d19000 0x6000     0x6000     com.shinywhitebox.iShowU-Audio-Capture (1.0.2) 5620A390-2E9D-32CA-9DC4-CBD6853E9890 <116 5 4 3>
  162    0 0xffffff7f83878000 0x1d000    0x1d000    com.intel.kext.intelhaxm (6.2.1) 7B6ABC56-699C-3449-A0EC-BEB36C154E3C <7 5 4 3 1>
  163    3 0xffffff7f83895000 0x64000    0x64000    org.virtualbox.kext.VBoxDrv (5.2.12) 3AABEB96-18B4-378E-B3EE-A0F6EB91DDE7 <7 5 4 3 1>
  171    0 0xffffff7f838f9000 0x8000     0x8000     org.virtualbox.kext.VBoxUSB (5.2.12) 9ABE1230-E87E-3B89-8E2A-B0B3BAA5F63D <170 163 52 7 5 4 3 1>
  172    0 0xffffff7f83901000 0x5000     0x5000     org.virtualbox.kext.VBoxNetFlt (5.2.12) 3EF145FE-B581-3F71-8F0F-E04C62C5A91D <163 7 5 4 3 1>
  173    0 0xffffff7f83906000 0x6000     0x6000     org.virtualbox.kext.VBoxNetAdp (5.2.12) F6F0D614-6816-3226-9263-DA96DB33D890 <163 5 4 1>


They're completely different ones from others posted here.

Attached is the kernel panic log.

[socratis]

I have experienced a crash like the ones described here.

Do you know what can cause a kernel panic? A gazillion of things...

both started by vagrant

Vagrant is a program that relies on VirtualBox but modifies its configuration files in unknown ways to us. It is not supported on these VirtualBox user forums, they have their own Vagrant support channels. If you are having this problem with a standalone version of VirtualBox, then we can continue this discussion.

they crashed when the boxes where being imported

Not sure what that means, care to explain it in more detail?

[SaulH]

@socratis

Please fill in the following questionnaire, because I'm getting a little confused (not enough caffeine). When starting the VM as follows, I get a kernel panic:
Command-line VBoxHeadles: Yes/No/Not applicable
Command-line VBoxManage: Yes/No/Not applicable
Right-click, start headless: Yes/No
Click the drop-down arrow on the Start icon: Yes/No/Not applicable

[socratis]

I'm sorry, but why did you select "Not applicable" in 3 out of 4. Does it crash like that yes, no, or you didn't even try? That's what the not applicable was aiming for actually, maybe I didn't put it in the correct terms...

[SaulH]

@socratis

I took "No" to mean I tried it, but it did not result in a panic. Most of those I did not try, so I described them as "not applicable".

[socratis]

Most of those I did not try

Well... that was the idea, wasn't it? To try and narrow down and see where and why you have a problem? *I* don't have a problem like that, if you catch my drift...