Page 2 of 2

Re: VirtualBox causing kernel panics

Posted: 30. Oct 2018, 15:23
by ./scc
Unfortunately, heading back to 5.2.18 VirtualBox continues to have this panic. I booted into Recovery so I could get the kernel backtrace symbolicated. Full one is attached, but here's the relevant top chunk.

Does anyone have any suggestions at all? Seriously I'd take anything.

Code: Select all

*** Panic Report ***
panic(cpu 2 caller 0xffffff800218776f): Kernel trap at 0xffffff80024d36b0, type 14=page fault, registers:
CR0: 0x0000000080010033, CR2: 0x00007fc0eb640a58, CR3: 0x00000003b76b9005, CR4: 0x00000000001627e0
RAX: 0xffffff8023eaf5d0, RBX: 0x00007fc0eb640a50, RCX: 0x0000000009000000, RDX: 0xffffff80028a5128
RSP: 0xffffff91ef163ea0, RBP: 0xffffff91ef163ef0, RSI: 0x0000000000000002, RDI: 0x0000000000000000
R8:  0x0000000000000000, R9:  0x0000000000000400, R10: 0xffffff9201b98380, R11: 0xffffff9201d81000
R12: 0xffffff91ef163ea0, R13: 0x0000000000000000, R14: 0xffffff80282107c0, R15: 0xffffff8002a2b8d0
RFL: 0x0000000000010206, RIP: 0xffffff80024d36b0, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x00007fc0eb640a58, Error code: 0x0000000000000000, Fault CPU: 0x2, PL: 0, VF: 1

Backtrace (CPU 2), Frame : Return Address
0xffffff91ef163970 : 0xffffff800206c1c6 mach_kernel : _handle_debugger_trap + 0x4c6
0xffffff91ef1639c0 : 0xffffff8002195274 mach_kernel : _kdp_i386_trap + 0x114
0xffffff91ef163a00 : 0xffffff8002187544 mach_kernel : _kernel_trap + 0x4e4
0xffffff91ef163a70 : 0xffffff800201e1e0 mach_kernel : _return_from_trap + 0xe0
0xffffff91ef163a90 : 0xffffff800206bc3c mach_kernel : _panic_trap_to_debugger + 0x21c
0xffffff91ef163bc0 : 0xffffff800206b9fc mach_kernel : _panic + 0x5c
0xffffff91ef163c20 : 0xffffff800218776f mach_kernel : _kernel_trap + 0x70f
0xffffff91ef163d90 : 0xffffff800201e1e0 mach_kernel : _return_from_trap + 0xe0
0xffffff91ef163db0 : 0xffffff80024d36b0 mach_kernel : _audit_mac_free + 0xa0
0xffffff91ef163ef0 : 0xffffff80024c5a65 mach_kernel : _audit_free + 0x115
0xffffff91ef163f10 : 0xffffff80024c6676 mach_kernel : _audit_syscall_exit + 0x46
0xffffff91ef163f40 : 0xffffff8002603987 mach_kernel : _unix_syscall64 + 0x287
0xffffff91ef163fa0 : 0xffffff800201e9c6 mach_kernel : _hndl_unix_scall64 + 0x16

BSD process name corresponding to current thread: VBoxHeadless
Boot args: -v keepsyms=1

Mac OS version:
17G65

Kernel version:
Darwin Kernel Version 17.7.0: Thu Jun 21 22:53:14 PDT 2018; root:xnu-4570.71.2~1/RELEASE_X86_64
Kernel UUID: 1AE5ACFD-3B6F-3D74-AD52-31F1430DBC6F
Kernel slide:     0x0000000001e00000
Kernel text base: 0xffffff8002000000
__HIB  text base: 0xffffff8001f00000
System model name: Macmini7,1 (Mac-35C5E08120C7EEAF)

System uptime in nanoseconds: 5815604575810
last loaded kext at 245369947881: com.apple.filesystems.msdosfs	1.10 (addr 0xffffff7f8542b000, size 69632)
last unloaded kext at 306144074409: com.apple.filesystems.msdosfs	1.10 (addr 0xffffff7f8542b000, size 69632)
loaded kexts:
org.virtualbox.kext.VBoxNetAdp	5.2.18
org.virtualbox.kext.VBoxNetFlt	5.2.18
org.virtualbox.kext.VBoxUSB	5.2.18
org.virtualbox.kext.VBoxDrv	5.2.18
Many, many thanks.
./scc

Re: VirtualBox causing kernel panics

Posted: 30. Oct 2018, 16:04
by pietpatat
Hey @pietpatat - was your system upgraded to High Sierra 10.13 from 10.12?
Looking at the release dates this is right around the time I bought this laptop, so it might have been on 10.13 from the start, not 100% sure on this.
Just stating the facts/dates here...
2018-07-09: 10.13.6 comes out. No major issues reported.
2018-10-16: 5.2.20 comes out.
2018-10-18: Unexplained kernel panic reports, start coming in.
Beware that I've encountered issues before 10.13.6 and 5.2.20. Not logged so maybe a bit of a useless statement as such, but just to give the complete information. I also just noticed I left out the dates in my combined log, but half of the kernel panics in that log were before 2018-10-16. (let me know if you need the full logs)
For this reason though, I don't see merit in going back to 5.2.18.

I did see there was a new macOS release last week, will upgrade to that soon and see how that goes.

Re: VirtualBox causing kernel panics

Posted: 30. Oct 2018, 23:45
by socratis
pietpatat wrote:I did see there was a new macOS release last week, will upgrade to that soon and see how that goes.
Are you talking about 10.14? Because I haven't seen a 10.13.7 coming out, not even mentioned on the webs...

Re: VirtualBox causing kernel panics

Posted: 31. Oct 2018, 10:44
by pietpatat

Re: VirtualBox causing kernel panics

Posted: 31. Oct 2018, 20:21
by ./scc
Yes, going to 10.14 is not an option at this point. Unless someone magically points me in the right direction I'm going to have to take larger steps (likely exporting those machines to a larger box/HD so I don't need to save the .vdi/disks through the thunderbolt cable).

Re: VirtualBox causing kernel panics

Posted: 1. Nov 2018, 04:25
by brycesteiner
10.14.x is not a good solution. VirtualBox with a windows 7 64bit guest is awful. I've never had a VirtualBox machine run this slow. It will pause for 30 seconds at a time just doing nothing. The mouse will still move though, but you can't click on anything. Then when shutting down the VM VirtualBox will close.

Re: VirtualBox causing kernel panics

Posted: 1. Nov 2018, 06:56
by socratis
@brycesteiner
Please don't post on each thread that has issues with 10.14. You already opened your own thread "Serious Lag with Windows 7 Guest", after posting in the "a lot of crashing in Mohave" thread, plus you do not have a kernel panic, so please do not post in the thread called "VirtualBox causing kernel panics", it dilutes and confuses.