Date: Wed, 02 Dec 2015 11:33:16 +0000 From: bugzilla-noreply@freebsd.org To: vbox@FreeBSD.org Subject: [Bug 201036] emulators/virtualbox-ose-kmod: kernel panic on boot in 10.2-PRERELEASE (10/stable) Message-ID: <bug-201036-26505-Zr3WLnPW6J@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-201036-26505@https.bugs.freebsd.org/bugzilla/> References: <bug-201036-26505@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201036 Pavlos Georgiadis <pavlos@georgiadis.eu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pavlos@georgiadis.eu --- Comment #3 from Pavlos Georgiadis <pavlos@georgiadis.eu> --- 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. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-201036-26505-Zr3WLnPW6J>