Since this pops up more and more frequently - a few bits of information: You can forget about running VirtualBox in Linux compatibility mode. The driver won't work.
Also, solving the build problems is also a relatively minor issue - it's simply bit rot since none of the VirtualBox developers had time to look into FreeBSD for more than a year now. The real problem is the FreeBSD kernel driver part of VirtualBox. That one is just partially done and was never working. Usually loading+unloading (without running a VM) already caused a kernel panic. So this is actually where the most work needs to be done - and that requires intimate knowledge of the FreeBSD kernel. Like reliably allocating a particular physical page and other unusual things. If you have that sort of knowledge, you're encouraged to contact us on #vbox (freenode). Note that we don't have enough resources to mentor Klaus _______________________________________________ vbox-dev mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-dev
