[gentoo] setting up bridged connection for virtualbox

[RabbieBurns]

Im going to follow this guide to try and get bridged networking going VirtualBox - Gentoo Linux Wiki, but the thing Im worried about is ive already got a TUN device created for openvpn, I dont want to break that..

 

eth0      Link encap:Ethernet  HWaddr 00:1e:0b:c6:81:c9  
         inet addr:192.168.2.12  Bcast:192.168.2.255  Mask:255.255.255.0
         inet6 addr: fe80::21e:bff:fec6:81c9/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:78047253 errors:0 dropped:10 overruns:0 frame:8
         TX packets:59585213 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000 
         RX bytes:56586542741 (52.7 GiB)  TX bytes:36909333385 (34.3 GiB)
         Interrupt:19 

lo        Link encap:Local Loopback  
         inet addr:127.0.0.1  Mask:255.0.0.0
         inet6 addr: ::1/128 Scope:Host
         UP LOOPBACK RUNNING  MTU:16436  Metric:1
         RX packets:1201243 errors:0 dropped:0 overruns:0 frame:0
         TX packets:1201243 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0 
         RX bytes:146355649 (139.5 MiB)  TX bytes:146355649 (139.5 MiB)

tun0      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
         inet addr:10.8.0.1  P-t-P:10.8.0.2  Mask:255.255.255.255
         UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
         RX packets:3740678 errors:0 dropped:0 overruns:0 frame:0
         TX packets:6109705 errors:0 dropped:48 overruns:0 carrier:0
         collisions:0 txqueuelen:100 
         RX bytes:290021203 (276.5 MiB)  TX bytes:7594846057 (7.0 GiB)

 

Will any of the stuff in the instructions to bridge to virtualbox break anything? I only have remote access to the server and cant afford to screw up the network.

[RabbieBurns]

Ok well it would seem that the latest virtualbox doesnt need me to mess with tun and tap. Result.

 

However Im still not sure how to get it working. I tried this:

 

VBoxManage modifyvm "2008Server" -nic1 hostif -hostifdev1 eth0:1

and a new eth0:1 interface appears on the host, but when I boot the guest windows operating system doenst pick up dhcp and setting it statically doesnt work.

[RabbieBurns]

If i just use eth0 instead of 0:1, I get this error:

 

Error: failed to start machine. Error message: Failed to initialize Host Interface Networking.
VBox status code: -3100 (VERR_HOSTIF_INIT_FAILED)

 

Google is not my friend with this, im stumbling upon the same error from lots of places..

 

eg [ubuntu] Virtualbox 2.1.2 headless on Ubuntu 8.10 Server [Archive] - Ubuntu Forums

[kmount]

Not tried this but the Gentoo Wiki link explains how to get around that error.

 

you may find that you you get an error when you try to start your VM. The error, ERR_HOSTIF_INIT_FAILED, will prevent you from stating the VM.

 

In order to fix it, you will need to modprobe the new vboxnetflt kernel module. You can find it in: /lib/modules//misc/vboxnetflt.ko. Simply change into that directory and run modprobe on the module, then restart your vm.

 

Tried that?

[RabbieBurns]

I havent tried that, when I read it I thought it was for only people upgrading from 2.1.. But its worth a shot anyway.

[RabbieBurns]

oasis ~ # cd /lib/modules/2.6.24-gentoo-r8/misc/

oasis misc # ls
vboxdrv.ko  vboxnetflt.ko  vmblock.ko  vmmon.ko  vmnet.ko

oasis misc # modprobe vboxnetflt   

oasis ~ # VBoxHeadless -startvm 2003Server
VirtualBox Headless Interface 2.0.2
(C) 2008 Sun Microsystems, Inc.
All rights reserved

Listening on port 3389
Error: failed to start machine. Error message: Failed to initialize Host Interface Networking.
VBox status code: -3100 (VERR_HOSTIF_INIT_FAILED)

 

Unfortunately not

 

Spent about 4 hours googling for this.. im just about to sign up to the vbox forums see if anyone there can help..

[RabbieBurns]

upgraded to version 3.0.0 and all problems went away..