Bug 203590
| Summary: | Fatal trap 12: with VirtualBox and VIMAGE | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Base System | Reporter: | Jimmy Olgeni <olgeni> | ||||||||
| Component: | kern | Assignee: | freebsd-emulation (Nobody) <emulation> | ||||||||
| Status: | Closed Works As Intended | ||||||||||
| Severity: | Affects Only Me | ||||||||||
| Priority: | --- | ||||||||||
| Version: | 10.2-STABLE | ||||||||||
| Hardware: | amd64 | ||||||||||
| OS: | Any | ||||||||||
| Attachments: |
|
||||||||||
Created attachment 161770 [details]
Panic traceback
Created attachment 161789 [details]
Kernel configuration
Virtualbox did not have VIMAGE enabled... |
Created attachment 161769 [details] Kernel configuration Using 10.2-STABLE FreeBSD 10.2-STABLE #4 r288916, I get a reproducible panic when starting VirtualBox. The panic started as soon as I enabled the VIMAGE option in the kernel. Kernel, userland and all modules from ports are aligned. Kernel configuration and panic data are attached. (I'm not even sure if VirtualBox is supposed to be able to run with VIMAGE enabled, so the fault might be expected)