Opened 8 years ago
Last modified 8 years ago
#16117 new defect
Kernel Panic on 10.10.1
| Reported by: | Majksner | Owned by: | |
|---|---|---|---|
| Component: | host support | Version: | VirtualBox 5.1.8 |
| Keywords: | Cc: | ||
| Guest type: | Linux | Host type: | Mac OS X |
Description
There is kernel panic when using virtualbox.
Attachments (2)
Change History (8)
by , 8 years ago
| Attachment: | VBoxSVC.log.7 added |
|---|
by , 8 years ago
| Attachment: | Kernel_2016-10-24-083312_Nikola.panic added |
|---|
comment:1 by , 8 years ago
comment:2 by , 8 years ago
And what exactly lead you to believe that it is VirtualBox that's responsible for the kernel panic? For all I know it crashed on the kernel_task and none of the kexts from VirtualBox are shown in the backtrace. It could be the "Viscosity VPN" for all I know. Does it happen often? Reproducible?
comment:3 by , 8 years ago
When I reverted back to Virtual Box 5.1.6 kernel panics stopped completely.
comment:4 by , 8 years ago
Also this topic mentions Virtual Box kext extensions could be a problem. Viscosity is the last extension loaded.
https://origin-discussions-us.apple.com/thread/7517504?start=0&tstart=0
comment:5 by , 8 years ago
No, it doesn't, it simply lists them as 3rd party extensions that are loaded, they blame Norton. The thing is that there have been zero reports so far with VirtualBox kernel panicking (KP) the host, that's why I'm a little bit skeptic.
- Did you try to uninstall Viscosity VPN and see if it changes the situation?
- What are you doing during the KP?
- Was even VirtualBox running?
comment:6 by , 8 years ago
I didn't uninstall Viscosity. Virtualbox was running and it was indexing data into ElasticSearch server on virtual machine when it happened. All kernel panics happened when Virtualbox was running no matter what I was doing in virtual machine. Also as I've mentioned reverting back to 5.1.6 kernel panics completely stopped.
Worth mentioning. https://googleprojectzero.blogspot.rs/2016/10/taskt-considered-harmful.html
"This post discusses a design issue at the core of the XNU kernel which powers iOS and MacOS. Apple have shipped two iterations of mitigations followed yesterday by a large refactor in MacOS 10.12.1/iOS 10.1."
It's 10.12.1 instead of 10.10.1 I'm sorry.