Hi all;
I have a vmware host which has 3 nic, one unplugged (eth0) and 2 connected to 2 network (eth1 and eth2).
I had configured vmnet0 as a bridge to eth2 and vmnet1 as a bridge to eth1:
\# ps -ef | grep bridge
root 4755 1 0 Jan03 ? 00:00:00 /opt/vmware/bin/vmnet-bridge -d /var/run/vmnet-bridge-0.pid /dev/vmnet0 eth2
root 4760 1 0 Jan03 ? 00:00:00 /opt/vmware/bin/vmnet-bridge -d /var/run/vmnet-bridge-2.pid /dev/vmnet2 eth1
I had setup some virtual server as guest, configuring one network card on vmnet0 and one on vmnet2.
I have ubuntu dapper on both host and guest.
My problem is this: sometimes (and I can't figure a schema) the network cards are detected by the guest as eth0 and eth1, using the vmxnet driver
#dmesg|grep eth
eth0: vmxnet ether at 0x1424 assigned IRQ 177
eth1: vmxnet ether at 0x14a4 assigned IRQ 185
Sometimes, instead, the network cards are detected as eth2 and eth3, using the PCnet driver:
\# dmesg|grep eth
eth0: registered as PCnet/PCI II 79C970A
eth1: registered as PCnet/PCI II 79C970A
eth3: no IPv6 routers present
eth2: no IPv6 routers present
I cannot figure how to avoid this behaviour: sometime rebooting the guest fix the problem, but I cannot find a reliable way to bind the eth to the vmxnet driver.
Any ideas ?