LinuxETC
September 27th, 2008, 03:06 PM
I figured I would post this since it is listed elsewhere in the forums, but similar issues. On a side note, do the items below via the VMware Server Console NOT via an ssh terminal since you will be bringing the network interfaces up/down.
The story goes that we upgraded the host (CentOS v5.2) VMware Server to 2.0 recently. Accordingly we started upgrading the VMware Tools in various guest systems too, including an Ubuntu 6.06LTS server and K/Ubuntu 8.04LTS desktop.
First item/issue, having vmxnet module loading properly:
What occurs here in particular with the "vmxnet" module is that one needs do the following (noted from a few VMware Server v1.0.x postings across the net as well):
Edit the /etc/modprobe.d/blacklist file to include the following line:
blacklist pcnet32
which is what a typical guest system install will auto detect in VMware Server v1.0.x and v2.0 installs. This will blacklist the pcnet32 modules from loading and letting the vmxnet to properly load for the guest. After this change is made, reboot the guest system, and you will note things should come up properly.
Second items/issue, having the network come up properly:
What occurred differently for us with the upgrade of VMware Tools to v2.0 is after a system (the guest here) reboot, the network interface would not come online. The results of /etc/init.d/networking start showed the following:
SIOCSIFADDR: No such device eth0
eth0: ERROR while getting interface flags: No such device
Further inspection via lsmod|grep vmxnet did show the module was loaded. Via another posting on the Ubuntu Forums:
http://ubuntuforums.org/showthread.php?t=221768
showed that by doing an ifconfig -a showed that the MAC address was swapped from eth0 to eth1. Editing the /etc/iftab with this little swap, then a system reboot, things came up fine.
HTH for others down the road.
LinuxETC
The story goes that we upgraded the host (CentOS v5.2) VMware Server to 2.0 recently. Accordingly we started upgrading the VMware Tools in various guest systems too, including an Ubuntu 6.06LTS server and K/Ubuntu 8.04LTS desktop.
First item/issue, having vmxnet module loading properly:
What occurs here in particular with the "vmxnet" module is that one needs do the following (noted from a few VMware Server v1.0.x postings across the net as well):
Edit the /etc/modprobe.d/blacklist file to include the following line:
blacklist pcnet32
which is what a typical guest system install will auto detect in VMware Server v1.0.x and v2.0 installs. This will blacklist the pcnet32 modules from loading and letting the vmxnet to properly load for the guest. After this change is made, reboot the guest system, and you will note things should come up properly.
Second items/issue, having the network come up properly:
What occurred differently for us with the upgrade of VMware Tools to v2.0 is after a system (the guest here) reboot, the network interface would not come online. The results of /etc/init.d/networking start showed the following:
SIOCSIFADDR: No such device eth0
eth0: ERROR while getting interface flags: No such device
Further inspection via lsmod|grep vmxnet did show the module was loaded. Via another posting on the Ubuntu Forums:
http://ubuntuforums.org/showthread.php?t=221768
showed that by doing an ifconfig -a showed that the MAC address was swapped from eth0 to eth1. Editing the /etc/iftab with this little swap, then a system reboot, things came up fine.
HTH for others down the road.
LinuxETC