Howdy,

I'm having an 'issue' with OES2 Linux running in a particular VM. I've
got a load of them running quite happily on my VMWare ESX system, but
this individual machine refuses to configure it's network card(s).

This has not always been the case: It survived long enough to get an
Informix database and data copied over to it, but at some point, it
stopped seeing the configuration for eth0/1/2.

It had one VM NIC, which ran with the vmxnet driver. When that went
south, there was a lot of modprobing, mucking about with pcnet32 and
vmxnet drivers, reinstallation of VMWare tools, all with the same
effect: when I did a /etc/init.d/network restart, I got the following:

londo:~ # /etc/init.d/network restart
Shutting down network interfaces:
eth0 No configuration found for eth0
Nevertheless the interface will be shut down. done
eth1 No configuration found for eth1
Nevertheless the interface will be shut down. done
Shutting down service network . . . . . . . . . . . . .
done.
Hint: you may set mandatory devices in /etc/sysconfig/network/config
Setting up network interfaces:
lo
lo IP address: 127.0.0.1/8 done
eth0 No configuration found for eth0 unused
eth1 No configuration found for eth1 unused
Setting up service network . . . . . . . . . . . . . .
done.
londo:~ #

boot.msg contains

Setting up network interfaces:
lo
lo IP address: 127.0.0.1/8 done
eth0 No configuration found for eth0 unused
eth1 No configuration found for eth1 unused

Waiting for mandatory devices: eth-bus-pci-0000:00:11.0 __NSC__
18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
eth-bus-pci-0000:00:11.0 No interface found


YaST reports the configuration is correct, and that the

/etc/sysconfig/network/ifcfg-eth-bus-pci-0000:00:11.0 and
/etc/sysconfig/network/ifcfg-eth-bus-pci-0000:00:12.0

files exist, containing the correct information.

Clue desperately needed!
Cheers,
--
James Dore,
New College IT Officer
it-support@new/james.dore@new
http://www.new.ox.ac.uk/