running a MBP Late 2016 with 10.12.6 with latest VirtualBox 5.1.26 r117224. Unfortunately I do get permanent kernel panic.
Code: Select all
Sun Aug 20 11:13:30 2017
*** Panic Report ***
panic(cpu 3 caller 0xffffff80079fe39d): Kernel trap at 0xffffff8007d2c590, type 13=general protection, registers:
CR0: 0x000000008001003b, CR2: 0x00000000018d1378, CR3: 0x000000002ed9212f, CR4: 0x00000000003627e0
RAX: 0x4318712137ee00cb, RBX: 0xdeadbeefdead002a, RCX: 0x0000000009000000, RDX: 0xffffff8008072138
RSP: 0xffffff9115b0bf10, RBP: 0xffffff9115b0bf30, RSI: 0xffffff8023ed9e00, RDI: 0x0000000000000000
R8: 0xffffff801ba42800, R9: 0xffffff8008072108, R10: 0x000070000e3a3ac0, R11: 0xffffff802e235b90
R12: 0x0000000000000000, R13: 0xffffff801bb30cc0, R14: 0xffffff801ba52db0, R15: 0xffffff80080ce5d0
RFL: 0x0000000000010282, RIP: 0xffffff8007d2c590, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x00000000018d1378, Error code: 0x0000000000000000, Fault CPU: 0x3, PL: 0, VF: 0
Backtrace (CPU 3), Frame : Return Address
0xffffff8109a65df0 : 0xffffff80078e953c
0xffffff8109a65e70 : 0xffffff80079fe39d
0xffffff8109a66050 : 0xffffff800789a593
0xffffff8109a66070 : 0xffffff8007d2c590
0xffffff9115b0bf30 : 0xffffff8007d1dfe5
0xffffff9115b0bf50 : 0xffffff8007e2413c
0xffffff9115b0bfb0 : 0xffffff800789ad96
BSD process name corresponding to current thread: VirtualBoxVM
Mac OS version:
16G29
Kernel version:
Darwin Kernel Version 16.7.0: Thu Jun 15 17:36:27 PDT 2017; root:xnu-3789.70.16~2/RELEASE_X86_64
Kernel UUID: D3314D98-5D40-3CD8-98A4-F1DD46C20E03
Kernel slide: 0x0000000007600000
Kernel text base: 0xffffff8007800000
__HIB text base: 0xffffff8007700000
System model name: MacBookPro13,1 (Mac-473D31EABEB93F9B)
System uptime in nanoseconds: 8195957431358
last loaded kext at 111654073647: com.apple.filesystems.smbfs 3.1.2 (addr 0xffffff7f88706000, size 425984)
loaded kexts:
com.symantec.kext.SymAPComm 100.1f12
org.virtualbox.kext.VBoxNetAdp 5.1.26
org.virtualbox.kext.VBoxNetFlt 5.1.26
org.virtualbox.kext.VBoxUSB 5.1.26
org.virtualbox.kext.VBoxDrv 5.1.26
....
Have already AppleDiagnostics (no issues) and a NVRAM reset. Problem still exists.
Any help is appreciated.