pcnet32 loaded instead of vmxnet

[jmc]

Running ubuntu jeos 8.04 beta and vmware esx 3.02, the network driver used by eth0 is pcnet32 instead of vmxnet.

During my testing of hardy beta on VMware ESX 3.0.2 I have so far found a problem with the network driver. I am using linux-virtual as my kernel.

As I understand it the pcnet32 driver should be replaced with the vmxnet driver. The kernel loads both the pcnet32 and the vmxnet driver.
This causes a problem since we need to rmmod both pcnet32 and vmxnet driver and then modprobe the vmxnet driver again and finally restart networking!

[Gerben (gerbenh)]

check also http://www.gerbenhoekstra.com/workaround-vmware-eth0-problems-with-ubuntu_jeos_710/

[jmc (thorlist)]

Gerben,
I tried to add ethernet0.virtualDev = “vmxnet” to the vmx file but it does not seems to make any difference (I am using vmware esx 3.02). The pcnet32 module is still loaded.

[Gerben (gerbenh)]

Ah i forgot to say in my blog it is for VMServer. For ESX 3 you should try ethernet0.virtualDev = “vlance” or try ethernet0.virtualDev = “e1000″
the vlance driver could be morphed internal to VMXNET when VMWareTools is installed.

[jmc (thorlist)]

Thanks for your help Gerben, unfortunately when I try ethernet0.virtualDev = “vlance”, it does not seem to have any effect, the pcnet32 driver is still loaded instead of vmxnet. Trying with e1000 doesn't work at all, the module does not seem to be included in the ubuntu jeos default installation.

[Daniel T Chen (crimsun)]

Is this symptom still reproducible in 8.10 or 9.04?

[Javier Jardón (jjardon)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!