networking problem on Open Solaris Developer Preview 2 guest

[mikael.ronstrom]

I was successful in installing VirtualBox on my Ubuntu 7.10 system
after some problems initially. I was also able to install the Open
Solaris Developer Preview 2 on the VirtualBox and get it started.

However to make it work in a useful manner one needs to create
a connection to the virtual Solaris machine and this is where I fail.

My plan was to set-up a static IP address such that I can use the
machine together with the other real machines in my local network.

The manual had good descriptions of how to set-up things on the
Ubuntu side by using a bridge and a TAP interface. After as usual
some problems I managed to set up a bridge br0 and a TAP device
tap0 with a static IP address 192.168.0.216 attached to them.

So this worked fine and the interface starts responding on ping
locally in the Linux box. Finally I also added the vbox0 as device
in VirtualBox and added that as the Host Interface for the virtual
machine.

However when I boot up the OpenSolaris VM it has no idea what
vbox0 is, and no idea of the IP address either. Also the manual
has no description of how to handle things in Solaris and I find
very little on the internet which can be directly applied.

So question is what I need to do to get it working if possible,

Rgrds Mikael
Here is the contents of my /etc/network/interfaces file:

auto eth0
iface eth0 inet static
address 192.168.0.206
netmask 255.255.255.0
gateway 192.168.0.1

iface br0 inet static
address 192.168.0.216
network 192.168.0.0
netmask 255.255.255.0
broadcast 192.168.0.255
gateway 192.168.0.1
bridge-ports eth0 tap0

auto tap0
iface tap0 inet static
address 192.168.0.216
netmask 255.255.255.0
tunctl_user mikael

[Sasquatch]

First, trash the IP settings on the slave interfaces, they are not needed and could cause problems. They will listen to the IP set on the bridge interface br0.
Next, in the VM you have to set an IP too. It doesn't automagically see what settings are on the other end. See it as two physical PCs connected with a cable with each other and only one has set an IP address. The other won't see it or do something with it.

[mikael.ronstrom]

First, trash the IP settings on the slave interfaces, they are not needed and could cause problems. They will listen to the IP set on the bridge interface br0.
Next, in the VM you have to set an IP too. It doesn't automagically see what settings are on the other end. See it as two physical PCs connected with a cable with each other and only one has set an IP address. The other won't see it or do something with it.

Great, thx
I dropped the eth0 and tap0 section which did the trick and connected
a new IP address in the Solaris VM and voila it worked.

Rgrds Mikael