vbox driver

[rondzierwa at comcast.net]

I think i got past this one with a quick hack. in mp-r0drv-freebsd.c, there are 
conditionals for kernel version >= 70000 that will use smp_rendezvous if the 
conditional is false. I simply hacked all the smp_rendezvous_cpus calls to 
smp_rendezvous. it loads and vbox seems to work. in osreldate.h my version 
is 700055, so i probably could have changed to if to be > 700055, but, since I 
wasn't sure when the smp_rendezvous_cpus function became available, it made 
no sense to me to come up with a more elegant patch, and i'm not really 
sure if my system is some sort of odd kludge. I installed 7.0 release, but 
csup'ed to the most recent kernel a couple of months later to get a more 
recent zfs. 

anyhow, I think i got it working on my machine. I'm trying to run a winxp guest 
that was created on vbox under windoze. I want to use the network adapter 
in bridged mode, but when i select "Bridged Adapter" on the network settings, 
a message appears in red in the text area at the bottom that says "no bridged 
network adapter is selected". There doesn't seem to be any place where I can 
select an adapter to which the vm can bridge. I do not recall having to specify 
anything on the windoze vbox when I set to bridged, and the windoze machine 
that I was running it on has two physical ethernet devices. it seemed to just 
pick one! The FreeBSD machine has only one physical ethernet device, a bge, 
so I would think the choices would be rather limited. 


thanks again, 
ron. 

----- Original Message ----- 
From: "Dan Nelson" <dnelson at allantgroup.com> 
To: "Gary Jennejohn" <gary.jennejohn at freenet.de> 
Cc: rondzierwa at comcast.net, freebsd-emulation at freebsd.org 
Sent: Sunday, July 5, 2009 12:40:25 PM (GMT-0500) Auto-Detected 
Subject: Re: vbox driver 

In the last episode (Jul 05), Gary Jennejohn said: 
> On Sat, 4 Jul 2009 17:09:33 +0000 (UTC) 
> rondzierwa at comcast.net wrote: 
> > I have installed the VirtualBox port my FreeBSD 7.0 system. I had to 
> > csup ports and download and install the virtualbox port manually, but 
> > eventually everything built and installed. 
> > 
> > kldload has a problem with the vboxdrv module: 
> > 
> > phoenix# kldload /boot/modules/vboxdrv.ko 
> > kldload: can't load /boot/modules/vboxdrv.ko: No such file or directory 
> > 
> > the file is there, and kldconfig is set up for the /boot/modules directory: 
> > 
> > phoenix# kldconfig -r 
> > /boot/kernel;/boot/modules 
> > phoenix# ls -l /boot/modules 
> > total 182 
> > -r-xr-xr-x 1 root wheel 185300 Jul 4 12:57 vboxdrv.ko 
> > 
> > could it be that there is no vboxdrv.ko.symbols file? all the other 
> > modules are in the /boot/kernel directory, and they all have .symbols 
> > files. 
> > 
> 
> This error message is confusing and doesn't necessarily really have 
> anything to do with vboxdrv.ko being present. kldload(2) in the kernel 
> can return a number of errors, but they're all hidden behind the error 
> message "can't load..." 
> 
> kldload(8) should probably use perror(3) so the user can see exactly 
> what the error returned from the kernel was. 

kldload did use perror; the kernel returned ENOENT - "No such file or 
directory". The problem is that the 92 defined errno values are not enough 
to describe all possible ways a syscall can fail. When loading a module, 
the most likely cause of ENOENT is a missing symbol preventing the linker 
from loading the module. The kernel will print a more verbose message to 
the console, so run dmesg and see what it's complaining about. 

-- 
Dan Nelson 
dnelson at allantgroup.com