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
+++ /etc/init.d/open-vm-tools 2009-01-19 10:51:49.000000000 +0100
@@ -67,6 +67,7 @@
then
modprobe -r pcnet32
modprobe vmxnet
+ invoke-rc.d udev restart
fi
log_daemon_msg "Starting open-vm guest daemon" "vmware-
guestd"
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).
--
network interface does not come up after installing open-vm-tools
https://bugs.launchpad.net/bugs/289921
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
