Bug 201036 - emulators/virtualbox-ose-kmod: kernel panic on boot in 10.2-PRERELEASE (10/stable)
Summary: emulators/virtualbox-ose-kmod: kernel panic on boot in 10.2-PRERELEASE (10/st...
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Virtualbox Team (Nobody)
URL:
Keywords: crash
Depends on:
Blocks:
 
Reported: 2015-06-22 06:14 UTC by Tony Narlock
Modified: 2018-02-15 22:51 UTC (History)
3 users (show)

See Also:
bugzilla: maintainer-feedback? (vbox)

Attachments
Screenshot of error (222.60 KB, image/jpeg)
2015-06-22 06:14 UTC, Tony Narlock 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tony Narlock 2015-06-22 06:14:17 UTC 
Created attachment 157972 [details]
Screenshot of error

VBoxDrvFreeBSDModuleEvent causes kernel panic on boot

stable/10 - r281836
virtualbox-ose-kmod-4.3.28

This kernel panic isn't producing a crash core file.

I can work around this temporarily by disabling `vboxdrv_load="YES"` inside /boot/loader.conf


What can I do to give better debug info?
Comment 1 rainbow 2015-06-22 17:45:41 UTC 
have you tried to rebuild kmod from ports?
I remember the "same" error..
Comment 2 Tony Narlock 2015-06-24 00:11:04 UTC 
Can someone change the version this to 10-stable?
Comment 3 Pavlos Georgiadis 2015-12-02 11:33:16 UTC 
I also get this on FreeBSD 9.3 with virbualbox-ose 4.3.34 (after upgrading from 4.3.24).

In my case the kernel modules seem to be loading fine (vboxdrv.ko, vboxnetflt.ko and 
vboxnetadp.ko). So with vboxnet_enable="YES" the system boots properly.

The kernel panic is caused when I add the vboxheadless_enable="YES" to rc.conf. Or if I try to start the VMs manually after booting. So it seems that the panic is caused when the VMs are starting.

In the kernel panic output I also saw the "spinlock held too long" message.
Comment 4 Walter Schwarzenfeld freebsd_triage 2018-01-13 00:01:34 UTC 
VBox version is at 5.2.4. 9.3 and 10.2 are gone. This is overcome by events.