problems with host interface

[phantom21]

I need to be able to demonstrate to a client we can setup a virtual windows server on the Linux server.

I've installed virtualbox 1.6 on the system and it uses NAT by default.

My system is an Acer Aspire 5102, AMD TL-50 dual core 64bit CPU, 1GB DDR2 RAM, built in ethernet and wireless, both of which work. My OS is Kubuntu 8.04LTS 64bit.

Using the instructions under help, I set up the host interface. Now, however, the guest system can't get outside (browse the internet from the guest), and while it seemed to work that I could see the samba shares from another system, now it doesn't work, and the samba shares don't show up.

The network interfaces file is this:

auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0


iface eth0 inet static
address 192.168.0.111
netmask 255.255.255.0
gateway 192.168.0.1

auto eth0

iface eth1 inet static
address 192.168.0.99
netmask 255.255.255.0
gateway 192.168.0.1

auto br0
iface br0 inet static
address 192.168.0.199
network 192.168.0.0
netmask 255.255.255.0
broadcast 192.168.0.255
gateway 192.168.0.1
bridge_ports eth0

I can ping, from an outside system, both the .111 and the .199 IP addresses.

I have setup the vbox0 in the settings for the guest, with host interface.

And there is another issue, which I know the work around.

Ever since setting up the bridge and modifying the interfaces file, when the system comes out of hibernation (the suspend mode doesn't work with hardy), I have to do the following:

1 - Go to another screen (ctrl-alt-fn)
2 - login in to the CLI
3 - check route, and generally find eth0 isn't in the route
4 - sudo ifconfig to setup the eth0
5 - get out of KDE
6 - startx
7 - restart both kontact and konquerer

Interestingly, if I don't do it, while I can't get email from kontact or browse in konquerer, FireFox browses with no problems.

[JshWright]

First off, eth0 doesn't need an IP address.

Secondly, there is a regression in 1.6 involving host networking that breaks hostif mode if you're using the AMD PCNet nictype. You have a few options:

1) Use the Intel nictype, since the regression doesn't show up with that nictype (assuming you're using the PUEL version)
2) Build the latest svn version, as that has the fix in it
3) Wait for 1.6.2 to be released (in the not too distant future)

[phantom21]

Well, I changed the NIC to the intel, installed the driver for it, and I'm still getting the same problem.

If I go the svn route, do I need to reinstall the windows in the newly created VirtualBox?

Since I'm scheduled to do the demo on Thursday, unless 1.6.2 comes out today or tomorrow, I may be up a creek without a paddle.

Mark