Page 1 of 1
Host-Interface doesn't work
Posted: 27. May 2008, 16:50
by sihelpdesk
Hi all!
I try to handle a Host-Interface on a Linux Ubuntu 8.04 Hardy 64Bit since two days and I'm getting crazy of it!
I followed exactly the instructions in the virtualbox manual:
editing and restarting networking service
Code: Select all
auto br0
iface br0 inet dhcp
bridge_ports eth0
adding a new interface with VBoxAddIF
and set the right settings in the VM-configuration.
But there is no way to ping a vaild IP address from the guest after I start them. I also set all rights and there is absolutly no error message when I boot the VM.
Do anyone have a idea?
Regards
Posted: 27. May 2008, 22:57
by Quantum
Hardy AMD64 here too, and also no luck. Except I have a WinXP guest over a Hardy host.
When I went to install XP it said Host Networking Interface error. Wish that worked, for security reasons. Do not want Winduhs touching the internets.
Code: Select all
Failed to initialize Host Interface Networking.
VBox status code: -3100 (VERR_HOSTIF_INIT_FAILED).
Result Code:
0x80004005
Component:
Console
Interface:
IConsole {d5a1cbda-f5d7-4824-9afe-d640c94c7dcf}
Posted: 27. May 2008, 23:24
by Sasquatch
Make sure that you use the Intel/Pro1000 NIC emulation first. Next, check when the VM is running what the command 'brctl show br0' says. It should say eth0, vbox0.
You can also try to add vbox0 to the interfaces file. Add vbox0 to the bridge_ports and add 'iface vbox0 inet manual'. That is how I have it set up. Works just fine.
Posted: 27. May 2008, 23:30
by Quantum
I've run VBoxAddIF, added vbox0 to /etc/network/interfaces, and ifup vbox0. I now have that interface. But still have the error on guest startup:
Code: Select all
Failed to initialize Host Interface Networking.
VBox status code: -3100 (VERR_HOSTIF_INIT_FAILED).
Result Code:
0x80004005
Component:
Console
Interface:
IConsole {d5a1cbda-f5d7-4824-9afe-d640c94c7dcf}
Posted: 27. May 2008, 23:46
by Quantum
Hang on, it seems the only way the instructions describe to set up host networking, is to set up a bridge to the outside. I don't want Winduhs touching the internets!
With VMware it has a vmnet driver which presents a vmnet0 interface to the host system with a defined IP address. The guest connects to the host through this interface, and is masqueraded through the host to the internets with the host's firewall protection.
I don't want to bridge the guest to the outside. Is there a way to set up host interface networking without the bridge?
Bridging and the ifcfg-br0 file
Posted: 29. May 2008, 03:03
by wyomingguy
I am fairly new to VirtualBox. I got the headless server up and running with bridging.
It appears to me that if the user you are using to run virtualbox is in the "vboxusers" group first, when you run the 'VBoxAddIF vbox0 <user> br0' command, it sets the correct permissions and adds all the devices.
However, I don't think it edits the ifcfg-br0 file for you.
Under the BRIDGE_PORTS= You MUST have more than just the eth0 in here.
The syntax may be different under SuSE than Ubuntu (whether you use tick marks or not.)
BRIDGE_PORTS='eth0 vbox0' is what I use in SuSE
also see
http://home.nyc.rr.com/computertaijutsu/vboxbridge.html
for a know problem in version 1.6
Posted: 29. May 2008, 10:16
by Sasquatch
Quantum wrote:Hang on, it seems the only way the instructions describe to set up host networking, is to set up a bridge to the outside. I don't want Winduhs touching the internets!
With VMware it has a vmnet driver which presents a vmnet0 interface to the host system with a defined IP address. The guest connects to the host through this interface, and is masqueraded through the host to the internets with the host's firewall protection.
I don't want to bridge the guest to the outside. Is there a way to set up host interface networking without the bridge?
HIF + No bridge = Virtual interface on Host only. With that, there is a two way communication possible from the host to the guest and guest to the host. The Guest won't be able to go further than the Host. You do have to set the right IP addresses on both ends.