RHEL5.2 eth0 show as inactive

[cristi4n]

im almost throwing the towel with this.

i created a rhel5.2 vm and the eth0 cant be activated.

so far i've tried the following without success

- installed vmware tools first

- i did "#/etc/init.d/network stop;rmmod pcnet32;rmmod vmxnet;modprobe vmxnet;/etc/init.d/network start"

- adding "check_link_down () { return 1; }" to the interface conf. file.

- removing ipv6

- add a second interface card and make the first one just local

- remove/manual add the interface.

- pray

and nothing, the interface stays as inactive.

any ideas ?

[Rockapot]

have you tried "ifconfig eth0 up"

Carl

[cristi4n]

yes, of course.

tried "ifup eth0" or "ifconfig eth0 up"

tried to activate with system-config-network

[admin]

32-bit or 64-bit? Client or server? What version of Fusion?

[cristi4n]

rhel5.2 client , 32bits kernel 2.6.18-92

vmware fusion 2.0.1

[powervm]

Check by re-installing VMTools in RHEL VM

[cristi4n]

yeah, thanks, did that and nothing, eth0 inactive.

however, im using the tar.gz , where can i get the rpm version ?

[WoodyZ]

however, im using the tar.gz , where can i get the rpm version ?

The VMware-tools-linux-116369.iso from Drivers & Tools contains an RPM however this is the Fusion 2.0.0 Build and I haven't see any update for Fusion 2.0.1 however I'd imagine it would work although be sure to backup the target Virtual Machine Document Package first.

Then again if you can't get it to work with the tar.gz I don't believe using the RPM is going to make any difference but maybe it's worth a try.

[cristi4n]

i end up creating a new vm, my previous vm had an absolute minimal installation so i guess there's a hidden dependency not noticeable during the installation of vmware tools

thanks everyone for the help.