[Solved] Hard crash (kernel panic) on macOS 10.14.5

Discussions related to using VirtualBox on Mac OS X hosts.

[Solved] Hard crash (kernel panic) on macOS 10.14.5

Postby ppinter1 » 18. May 2019, 17:09

I have several VBox Guests for legacy support work with various Windows and Linux VMs.

Checking my InstallHistory.plist file, I upgraded to VBox 6.0.8 on 5/15@11:53 and all Guest VMs worked fine.

Later the same day 5/15@16:27, the macOS 10.14.5 upgrade was offered. I reviewed the changelog and upgraded.

However, since upgrading macOS, I began seeing a fairly consistent crash when starting any VBox Guest instance.

I wasn't willing to downgrade macOS, so I ran the VirtualBox_uninstall.tool script and re-installed VBox 6.0.6.

(Yes, I first needed to apply the magic incantation "spctl kext-consent add VB5E2TV963" in Recovery Mode).

Regrettably, VBox 6.0.6 still hard crashes on starting any Guest VM. The macOS crash log begins:

Code: Select all   Expand viewCollapse view
*** Panic Report ***
panic(cpu 12 caller 0xffffff8019adb92d): Kernel trap at 0xffffffa3e1565f56, type 14=page fault, registers:
CR0: 0x0000000080010033, CR2: 0x00007fb038416000, CR3: 0x0000000860c06117, CR4: 0x00000000000226e0
RAX: 0x0000000000000000, RBX: 0x00007faff823ed44, RCX: 0x0000000000000200, RDX: 0x0000000000000319
RSP: 0xffffffa3de183c60, RBP: 0xffffffa3de183d00, RSI: 0x00007faff8218000, RDI: 0x00007fb038416000
R8:  0x00007faff823ed18, R9:  0x00007faff823ed78, R10: 0x0000000000000000, R11: 0x00007faff823ed42
R12: 0x00007faff823ed40, R13: 0x0000000000016c00, R14: 0x00007faff823ed38, R15: 0x00007faff823ed18
RFL: 0x0000000000010246, RIP: 0xffffffa3e1565f56, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x00007fb038416000, Error code: 0x0000000000000002, Fault CPU: 0xc, PL: 1, VF: 5

Backtrace (CPU 12), Frame : Return Address
0xffffffa3de183730 : 0xffffff80199aea2d
.
.
.

Kernel Extensions in backtrace:
         org.virtualbox.kext.VBoxDrv(6.0.6)[96C33780-8C46-3129-B202-5823404C4DA0]@0xffffff7f9e338000->0xffffff7f9e427fff

BSD process name corresponding to current thread: VirtualBoxVM

Mac OS version:
18F132

Kernel version:
Darwin Kernel Version 18.6.0: Thu Apr 25 23:16:27 PDT 2019; root:xnu-4903.261.4~2/RELEASE_X86_64


I've issued crash logs via the 'Send to Apple' dialog prompt, but the VBox engineers really need to see this.

What's the suggestion here: Is there any point to further downgrading to VBox 6.0.4?

(I can sometimes get into a Guest VM without crashing, but it's not bankable)
Last edited by ppinter1 on 20. May 2019, 15:41, edited 1 time in total.
ppinter1
 
Posts: 8
Joined: 8. Nov 2011, 23:33
Primary OS: Mac OS X other
VBox Version: OSE other
Guest OSses: linux

Re: Hard crash (kernel panic) on macOS 10.14.5

Postby socratis » 18. May 2019, 18:31

ppinter1 wrote:I've issued crash logs via the 'Send to Apple' dialog prompt, but the VBox engineers really need to see this.

I suspect that the developers might want to see the whole log, ZIPPED, not just portions of it.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
socratis
Site Moderator
 
Posts: 25221
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Re: Hard crash (kernel panic) on macOS 10.14.5

Postby ppinter1 » 18. May 2019, 20:31

Yes indeed. And, I even meant to attach the full crash report, but it neatly slipped my mind.

Regardless, I've attached it here.

Thanks,
/p2
Attachments
macOS_VBox_Crash.log.zip
(3.89 KiB) Downloaded 17 times
ppinter1
 
Posts: 8
Joined: 8. Nov 2011, 23:33
Primary OS: Mac OS X other
VBox Version: OSE other
Guest OSses: linux

Re: Hard crash (kernel panic) on macOS 10.14.5

Postby socratis » 19. May 2019, 00:40

com.intel.kext.intelhaxm                  7.3.2
com.Logitech.Control Center.HID Driver 3.9.8

We've seen several conflicts with those two extensions, a search for either returns plenty of results. Can you uninstall or check if there are updates to either of these two?
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
socratis
Site Moderator
 
Posts: 25221
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Re: Hard crash (kernel panic) on macOS 10.14.5

Postby ppinter1 » 20. May 2019, 15:40

I'm pleased to report that after uninstalling both LCC and HAXM, VirtualBox is stable again!

I've even upgraded to VBox 6.0.8 to remain on a supported codebase.

Thank you very much for your work diagnosing this, socratis.

I'll be raising a glass of tsipouro to your health today,

Yiamas!
ppinter1
 
Posts: 8
Joined: 8. Nov 2011, 23:33
Primary OS: Mac OS X other
VBox Version: OSE other
Guest OSses: linux

Re: [Solved] Hard crash (kernel panic) on macOS 10.14.5

Postby socratis » 20. May 2019, 17:09

Glad I could help. And thank you for marking the topic as [Solved]. And of course... Yiamas! :D
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
socratis
Site Moderator
 
Posts: 25221
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Re: [Solved] Hard crash (kernel panic) on macOS 10.14.5

Postby nean.0 » 11. Jun 2019, 17:26

Can I reopen this thread?

I have the exact same problem as described by ppinter1. I can't run any VM guests any longer after upgrading to 10.14.5. Sometimes I can boot and login before it crashes. Often it will crash immediately at login to the VM. I first noticed the problem when all my suspended VMs would cause a crash when resuming.

Attached is crash report. The kernel extensions that caused the problems for ppinter1 are not installed on my Mac.
$ kextstat | grep -v com.apple
Index Refs Address Size Wired Name (Version) UUID <Linked Against>
111 3 0xffffff7f83eaa000 0x66000 0x66000 org.virtualbox.kext.VBoxDrv (5.2.28) B48016E5-F1F0-3171-8632-6409DC4A3DD7 <8 6 5 3 1>
169 0 0xffffff7f84843000 0x8000 0x8000 org.virtualbox.kext.VBoxUSB (5.2.28) DDEC6151-6E69-380A-93AC-13BD099AEE77 <168 111 56 8 6 5 3 1>
175 0 0xffffff7f84884000 0x5000 0x5000 org.virtualbox.kext.VBoxNetFlt (5.2.28) ACC4F548-53A7-3AC8-B675-FDF2FBB8AFB5 <111 8 6 5 3 1>
179 0 0xffffff7f8493c000 0x5000 0x5000 com.nomachine.driver.nxau (4.1.b2) 78172556-B6A4-3112-BA41-E79D18108476 <133 6 5 3 1>
186 0 0xffffff7f859fe000 0x6000 0x6000 org.virtualbox.kext.VBoxNetAdp (5.2.28) 199A5D33-4096-33B5-89AD-7C5298C85D49 <111 6 5 1>
Attachments
vbox.log.zip
VBox.log
(25.92 KiB) Downloaded 5 times
crash.zip
One of the crash reports
(240.26 KiB) Downloaded 5 times
nean.0
 
Posts: 13
Joined: 11. Jun 2019, 17:06

Re: [Solved] Hard crash (kernel panic) on macOS 10.14.5

Postby dvmierlo » 15. Jun 2019, 11:46

I have the same issue. It looks like that this macOS crash was happening when resuming vm's that where suspended before the update to 10.14.5. After reverting the vm to it's powered off state and do a fresh boot, it runs fine. Is this the same in your situation?
dvmierlo
 
Posts: 1
Joined: 15. Jun 2019, 11:23

Re: [Solved] Hard crash (kernel panic) on macOS 10.14.5

Postby nean.0 » 17. Jun 2019, 16:09

It's difficult to diagnose. I do my main work in one particular VM (OpenSUSE) and I managed to start it and have for this reason so far not tried to suspend it or reboot since I wrote last. I only pause it for the time being and let the Mac do its own thing when I close the lid.

This means that I have not been able to start any other 3 VMs since I allocate pretty much all resources to this VM. The Mac is only a host for me and not much more except for Outlook (and on occasion MS Teams) which we use at the company for email.

Funny thing is that there seems to be so many problems associated with the new generations of Macs. On my old Macbook Pro from 2015 I have the exact same VMs (since I cloned from it) but it does not have these problems with MacOS 10.14.5. I can suspend and resume on the older hardware without problems.

Not to mention how it's impossible to run the VMs on the laptop screen on this Macbook Pro 2018. It is literally impossible because of the lagging. But when I connect to an external screen then it works reasonably. What is that about?
nean.0
 
Posts: 13
Joined: 11. Jun 2019, 17:06


Return to VirtualBox on Mac OS X Hosts

Who is online

Users browsing this forum: No registered users and 13 guests