Opened 10 years ago
Closed 9 years ago
#14695 closed defect (fixed)
[El Capitan] Kernel Panic on VM shutdown
Reported by: | steinharts | Owned by: | |
---|---|---|---|
Component: | host support | Version: | VirtualBox 5.0.6 |
Keywords: | Cc: | ||
Guest type: | Windows | Host type: | Mac OS X |
Description
I had a kernel panic while shutting down a windows 8.1 virtual machine. Attached the logs.
Attachments (2)
Change History (9)
by , 10 years ago
Attachment: | VirtualBox_shutdown_kernel_panic.log added |
---|
comment:2 by , 10 years ago
Also confirming this happens in El Capitan with a Windows 7 guest. I think it's actually happening for any guest for me as long as I connect at least one USB device.
comment:3 by , 9 years ago
Version 5.0.12 r104815. Host = El Cap. Guest = Windows 7. Extension pack installed: Oracle_VM_VirtualBox_Extension_Pack-5.0.12-104815.vbox-extpack. Guest additions also installed. Kernel panic occurs when attempting to shutdown while there is an existing USB connection. No kernel panic on shutdown without an existing USB connection. Kernel panic also occurs when attempting to disconnect existing USB connection (without shutdown).
comment:4 by , 9 years ago
Same happens for me, panic on shutdown. Seems related to using USB. Version 5.0.12 r104815 w/extensions and additions installed. Host: El Capitan. Guest: Window 10. Top of panic log below.
Anonymous UUID: DBFD2831-99F0-F3A7-9EAC-8F11930339EB Tue Jan 5 14:12:01 2016 *** Panic Report *** panic(cpu 0 caller 0xffffff8003dd155a): Kernel trap at 0xffffff8018e9f5e0, type 14=page fault, registers: CR0: 0x000000008001003b, CR2: 0xffffff8018e9f5e0, CR3: 0x000000024f3ae079, CR4: 0x00000000001626e0 RAX: 0xffffff80164b0000, RBX: 0x000000000000001e, RCX: 0xffffff80152abc08, RDX: 0x0000000000000001 RSP: 0xffffff810e3f3c78, RBP: 0xffffff810e3f3ca0, RSI: 0x0000000000000001, RDI: 0xffffff802229ca00 R8: 0x000000000000ffff, R9: 0x0000000000000001, R10: 0xffffff801c2651bc, R11: 0xffffff80042b70e0 R12: 0x000000000000001e, R13: 0x0000000000050001, R14: 0xffffff7f84b1b808, R15: 0xffffff801927f400 RFL: 0x0000000000010286, RIP: 0xffffff8018e9f5e0, CS: 0x0000000000000008, SS: 0x0000000000000010 Fault CR2: 0xffffff8018e9f5e0, Error code: 0x0000000000000011, Fault CPU: 0x0 Kernel NX fault, PL: 0 Backtrace (CPU 0), Frame : Return Address 0xffffff810e3f3900 : 0xffffff8003cde792 0xffffff810e3f3980 : 0xffffff8003dd155a 0xffffff810e3f3b60 : 0xffffff8003def233 0xffffff810e3f3b80 : 0xffffff8018e9f5e0 0xffffff810e3f3ca0 : 0xffffff800423bb81 0xffffff810e3f3cd0 : 0xffffff800423b9c6 0xffffff810e3f3cf0 : 0xffffff8003d94deb 0xffffff810e3f3d30 : 0xffffff8003ce2f18 0xffffff810e3f3d60 : 0xffffff8003cc68a8 0xffffff810e3f3da0 : 0xffffff8003ce3356 0xffffff810e3f3dd0 : 0xffffff8003ccee6c 0xffffff810e3f3e50 : 0xffffff8003cd180c 0xffffff810e3f3ea0 : 0xffffff8003d0234a 0xffffff810e3f3ee0 : 0xffffff800419c9e8 0xffffff810e3f3f50 : 0xffffff800419c73c 0xffffff810e3f3f60 : 0xffffff8004229ac1 0xffffff810e3f3fb0 : 0xffffff8003defa36 BSD process name corresponding to current thread: VirtualBoxVM Mac OS version: 15C50 Kernel version: Darwin Kernel Version 15.2.0: Fri Nov 13 19:56:56 PST 2015; root:xnu-3248.20.55~2/RELEASE_X86_64 Kernel UUID: 17EA3101-D2E4-31BF-BDA9-931F51049F93 Kernel slide: 0x0000000003a00000 Kernel text base: 0xffffff8003c00000 __HIB text base: 0xffffff8003b00000 System model name: MacBookAir5,2 (Mac-2E6FAB96566FE58C) System uptime in nanoseconds: 33970186813844 last loaded kext at 33238429419418: com.apple.driver.IOBluetoothHIDDriver 4.4.3f4 (addr 0xffffff7f868e9000, size 73728) last unloaded kext at 29015042753456: com.apple.driver.IOBluetoothHIDDriver 4.4.3f4 (addr 0xffffff7f868e9000, size 73728) loaded kexts: org.virtualbox.kext.VBoxNetAdp 5.0.12 org.virtualbox.kext.VBoxNetFlt 5.0.12 org.virtualbox.kext.VBoxUSB 5.0.12 org.virtualbox.kext.VBoxDrv 5.0.12 com.apple.filesystems.smbfs 3.0.0 com.apple.driver.AudioAUUC 1.70
follow-up: 6 comment:5 by , 9 years ago
We would need to have the crash dump available to find the reason for this panic.
Could you also test the most recent 5.0 Mac OS X test build (>= 105008) and test if it makes any difference? Thank you!
comment:6 by , 9 years ago
Replying to frank:
We would need to have the crash dump available to find the reason for this panic.
Could you also test the most recent 5.0 Mac OS X test build (>= 105008) and test if it makes any difference? Thank you!
Now running Version 5.0.13 r105025 and it seems fixed! Until this version, ever since upgrading to El Capitan, I was getting 100% kernel panics on shutdown after using USB. Looking good, thanks.
comment:7 by , 9 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Thanks for testing! The fixes are part of VBox 5.0.14. Please reopen if still relevant with VBox 5.0.14.
OS X error report after kernel panic