Discussion:
[packages/open-vm-tools] we don't provide vmxnet module, drop support for it
Jan Palus
2018-09-04 11:23:45 UTC
Permalink
commit 21d43020dfd7dc915c941739408c48f91b9681f5
Date: Sun Sep 2 18:03:55 2018 +0200
we don't provide vmxnet module, drop support for it
I'm not using PLD in VMware VM anymore, but please keep in mind vmxnet module is
now part of mainline kernel, though apparently it's called vmxnet3 nowadays.
Adam Golebiowski
2018-09-09 17:47:19 UTC
Permalink
Post by Jan Palus
commit 21d43020dfd7dc915c941739408c48f91b9681f5
Date: Sun Sep 2 18:03:55 2018 +0200
we don't provide vmxnet module, drop support for it
I'm not using PLD in VMware VM anymore, but please keep in mind vmxnet module is
now part of mainline kernel, though apparently it's called vmxnet3 nowadays.
I know, but I don't think we should unconditionally load this module and
let the user handle it on his own (for example with modprobe.conf
entry).

After all, this is just network card module, how does this differ
from igb, e1000e or 8139too ?

At the same time we could wonder whether this init should modprobe
vmw_pvscsi - if this is your rootfs device, than you have this already
loaded, if not than either you don't need it (using different device
type), or have unusual setup that you handle with care anyway.

In fact, I think I'll drop vmw_pvscsi part as well.

adamg

Loading...