As for some reason the hardware change initiated by the guest tools isn't noticed by udev. Restarting udev does detect it. There might be a better way to signal udev in this case, but I don't know enough details about udev to figure that out.
I'd say this solution is better than modifying initrd, as it now only loads the vmxnet module when needed (and not always which is the case with a modified initrd).
I have another works-for-me (tm) solution (other than adding vmxnet to initrd):
Modify /etc/init. d/open- vm-tools:
--- /etc/init. d/open- vm-tools. orig 2009-01-19 10:57:02.000000000 +0100 d/open- vm-tools 2009-01-19 10:51:49.000000000 +0100
then
modprobe -r pcnet32
modprobe vmxnet
+++ /etc/init.
@@ -67,6 +67,7 @@
+ invoke-rc.d udev restart
fi
As for some reason the hardware change initiated by the guest tools isn't noticed by udev. Restarting udev does detect it. There might be a better way to signal udev in this case, but I don't know enough details about udev to figure that out.
I'd say this solution is better than modifying initrd, as it now only loads the vmxnet module when needed (and not always which is the case with a modified initrd).