Date: Wed, 10 Feb 2010 22:18:22 -0800 From: Yuri <yuri@rawbw.com> To: Bernhard Froehlich <decke@bluelife.at> Cc: vbox@freebsd.org, freebsd-questions@freebsd.org, Bernt Hansson <bernt@bah.homeip.net> Subject: Re: VirtualBox is broken? Message-ID: <4B73A12E.2050906@rawbw.com> In-Reply-To: <bef835cd31944ed4557e31715fc04b04@bluelife.at> References: <4B71B476.5020909@rawbw.com> <4B71C309.6000103@bah.homeip.net> <bef835cd31944ed4557e31715fc04b04@bluelife.at>
next in thread | previous in thread | raw e-mail | index | archive | help
Bernhard Froehlich wrote: > Have a look at /var/log/messages and see what gets logged there when > trying to load the module. Probably your Kernel sources and the vbox > module are out of date or you hit a bug. > This is the only line that gets printed into the log on module load: Feb 9 13:24:35 myhost kernel: vboxdrv: fAsync=0 offMin=0x1f64 offMax=0x2688 Not a chance of kernel sources being outdated or out of sync with vbox. Kernel userland were just rebuilt from the recent sources. And vbox still crashes the system. Do you actually have the latest vbox working with the latest 8.0-STABLE kernel? > Please read http://wiki.freebsd.org/VirtualBox on how to correctly > load the module because you risk a freeze when loading it with > kldload when running. > I am pretty much doing the same as in this wiki-page. Yuri
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B73A12E.2050906>