2017-05-18 12:38 GMT+03:00 Rodney W. Grimes <
> This is a long standing issue with VMware ESXi, it effects
> Linux as well as FreeBSD and Windows.   A couple of googles
> for things like
> Well lead you to several articles talking about this issue.
> I did not find any solutions however.

Did you try edit vmx hardware config?

I googled solution for RHEL6:
# cat /etc/udev/rules.d/69-vmxnet3-net.rules
SUBSYSTEM=="net", ACTION=="add", KERNELS=="0000:0b:00.0"
DRIVERS=="vmxnet3", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", KERNELS=="0000:13:00.0"
DRIVERS=="vmxnet3", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"
SUBSYSTEM=="net", ACTION=="add", KERNELS=="0000:1b:00.0"
DRIVERS=="vmxnet3", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"

Do we have similar technique for mapping pci id to driver/name?


> --
> Rod Grimes
freebsd-virtualization@freebsd.org mailing list
To unsubscribe, send any mail to 

Reply via email to