vbox driver

Sun Jul 5 20:55:50 UTC 2009

ok, so if i use nat, i can ping and telnet to the bsd machine that is hosting 
the vm. on the client, ipconfig -all returns an ethernet adapter with an ip 
address of 10.0.2.15, and a gateway of 10.0.2.2. I can telnet to 10.0.2.2 
(the bsd host), but from there I can't get back to the client (10.0.2.2) 

there are no pseudo network interfaces on the host, and there are no 
routes to the client defined, so i'm a little stymed as to how the telnet 
connection from the client to the host is working. is this some sort of 
one-way-networking, or am i missing a configuration step? 

how can I connect to network resources that exist outside of the host 
machine? More importantly, since the client that I am running is a 
server of sorts, how can other machines on my local network access it? 

ron. 

----- Original Message ----- 
From: "Martin Wilke" <miwi at FreeBSD.org> 
To: rondzierwa at comcast.net 
Sent: Sunday, July 5, 2009 4:12:53 PM (GMT-0500) Auto-Detected 
Subject: Re: vbox driver 

-----BEGIN PGP SIGNED MESSAGE----- 
Hash: SHA1 

On Sun, Jul 05, 2009 at 07:53:51PM +0000, rondzierwa at comcast.net wrote: 
> 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. 

At the moment not supported by vbox. 

> 
> 
> 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 
> _______________________________________________ 
> freebsd-emulation at freebsd.org mailing list 
> http://lists.freebsd.org/mailman/listinfo/freebsd-emulation 
> To unsubscribe, send any mail to "freebsd-emulation-unsubscribe at freebsd.org" 
> 

- -- 

+-----------------------+-------------------------------+ 
| PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de | 
| Skype : splash_111 | Mail : miwi(at)FreeBSD.org | 
+-----------------------+-------------------------------+ 
| Mess with the Best, Die like the Rest! | 
+-----------------------+-------------------------------+ 
-----BEGIN PGP SIGNATURE----- 
Version: GnuPG v2.0.11 (FreeBSD) 

iEYEARECAAYFAkpRCUUACgkQdLJIhLHm/Ol7pwCeP5cpDUVhipZY8fj/EWkaXInt 
vq4AniCqdvMGw6l4DXq6Eij6NIuisLpi 
=jELy 
-----END PGP SIGNATURE----- 