Not knowing whether or not having both pcnet32 and vmxnet modules loaded, I
found a work around that consistently shows only:
$ lsmod | egrep 'vm|pcnet'
vmsync 3836 0
vmmemctl7388 0
vmhgfs 33376 0
vmxnet 13696 0
I think this wo
It's possible that I missed something else, but after following the same
steps, on a similar guest host (Lenny, after apt-get update/upgrade), the
end result is that vmxnet is not loaded after reboot.
Here is a relevant piece of dpkg -s open-vm-tools in that environment:
Version: 2008.11.18-13022
You and I evidently have different interpretations of what 'broken' means.
I've gotten used to apt-get install foo doing everything necessary to get a
package working after being issued. This includes modules for kernel video
drivers, but that is on Ubuntu. Perhaps Ubuntu has a different theory o
3 matches
Mail list logo
