I was in hurry yesterday evening, so here is information what I#ve done:
Installed Solaris 11.1 with all upgrades; installed VirtualBox 2.4.6; netconfiguration after that:
~# dladm
LINK CLASS MTU STATE OVER
net1 phys 1500 unknown --
net2 phys 1500 up --
net3 phys 1500 unknown --
vboxnet0 phys 1500 up --
net0 phys 1500 unknown --
root@neumann:~# ipadm
NAME CLASS/TYPE STATE UNDER ADDR
lo0 loopback ok -- --
lo0/v4 static ok -- 127.0.0.1/8
lo0/v6 static ok -- ::1/128
net2 ip ok -- --
net2/v4 static ok -- xxx.xxx.xxx.xxx/24
net2/v6 addrconf ok -- fe80::e2db:55ff:fe09:1894/10
networking profile is DefautFixed configured by Solaris-installation 'cause I've
configured it with fixed addresses (IP, netmask, nameserver, ...)
Ubuntu-12.04-Server-VMs are installed with following config:
HDDs as *.vdi-file, bridged networking choosing one netx-Link per VM and
netx-Links are not configured using "ipadm create-ip netx" and no vnics are
defined in Solaris; they are created by VirtualBox after starting VMS
Modules:
# modinfo | grep vbox
192 fffffffff7ea95b8 ce0 304 1 vboxnet (VirtualBox NetAdp 4.2.6r82870)
194 fffffffff7f67000 34f00 303 1 vboxdrv (VirtualBox HostDrv 4.2.6r82870)
249 fffffffff8ae9000 3828 305 1 vboxbow (VirtualBox NetBow 4.2.6r82870)
250 fffffffff8aed000 4580 306 1 vboxusbmon (VirtualBox USBMon 4.2.6r82870)
251 fffffffff8af2000 7478 307 1 vboxusb (VirtualBox USB 4.2.6r82870)
after starting all VMs for the first time, everything works fine with this:
# dladm
LINK CLASS MTU STATE OVER
net1 phys 1500 up --
net2 phys 1500 up --
net3 phys 1500 up --
vboxnet0 phys 1500 up --
net0 phys 1500 up --
vboxvnic0 vnic 1500 up net3
vboxvnic1 vnic 1500 up net0
vboxvnic2 vnic 1500 up net1
# ipadm
NAME CLASS/TYPE STATE UNDER ADDR
lo0 loopback ok -- --
lo0/v4 static ok -- 127.0.0.1/8
lo0/v6 static ok -- ::1/128
net2 ip ok -- --
net2/v4 static ok -- 132.230.153.100/24
net2/v6 addrconf ok -- fe80::e2db:55ff:fe09:1894/10
ping, ssh, ... is working as expected.
If I shutdown dladm says:
# dladm
LINK CLASS MTU STATE OVER
net1 phys 1500 up --
net2 phys 1500 up --
net3 phys 1500 up --
vboxnet0 phys 1500 up --
net0 phys 1500 up --
If I start VMs again, it looks like this
# dladm
LINK CLASS MTU STATE OVER
net1 phys 1500 up --
net2 phys 1500 up --
net3 phys 1500 up --
vboxnet0 phys 1500 up --
net0 phys 1500 up --
vboxvnic3 vnic 1500 up net3
vboxvnic4 vnic 1500 up net0
vboxvnic5 vnic 1500 up net1
but i can't ping, ssh, ... to any VM and if I log in any VM using VM VirtualBoxManager
everything in VM output of ethernet addess, inet address, ... is ok but eth0 in not "up"
and therefore I have no network connection. After Rebooting the server with every netx-Link
being in state "unknown" starting VMs again works well.
Questions (in easy words
:
- is there a possibility to put netx-Links in state "unknown" or "down" 'cause it seems to me
that starting a VM with netx_link in state "up" doesn't work?
- on the other hand is it possible to "bind" a netx-Link to vboxnicx (that's the second difference
I see, that starting VMs once again vboxnicx are incremented)
- do I have to configure netx-Links with "ipadm create-ip netx"?
Regards
Wolfgang