Everyone in my office uses VMWare Fusion 1.1 to run Ubuntu ( although a few brave souls have gone native ).
We've all run into this bug one by one. Most have settled for the disable-roaming workaround. I tried this, and couldn't get it to work. I had to manually run: ifconfig eth0 up & dhclient.
I ran a bunch of tests to see if I could figure this out and it looks to me like this is a bug in either the vmxnet driver or the vmware-config-tool.pl script which is supposed to be run after vmware-install-tools.pl.
I posted a new discussion detailing my testing on the VMWare Fusion forum:
FYI, in addition to the missing 'device' links in /sys/class/net/eth0, the driver link in the corresponding pci device looks incorrect, and there's also a missing "net:eth0" link in the device dir as well. See my VMWare post for the details.
Everyone in my office uses VMWare Fusion 1.1 to run Ubuntu ( although a few brave souls have gone native ).
We've all run into this bug one by one. Most have settled for the disable-roaming workaround. I tried this, and couldn't get it to work. I had to manually run: ifconfig eth0 up & dhclient.
I ran a bunch of tests to see if I could figure this out and it looks to me like this is a bug in either the vmxnet driver or the vmware- config- tool.pl script which is supposed to be run after vmware- install- tools.pl.
I posted a new discussion detailing my testing on the VMWare Fusion forum:
http:// communities. vmware. com/thread/ 118348? tstart= 0
FYI, in addition to the missing 'device' links in /sys/class/ net/eth0, the driver link in the corresponding pci device looks incorrect, and there's also a missing "net:eth0" link in the device dir as well. See my VMWare post for the details.