** Summary changed: - network interface does not come up after installing open-vm-tools + SRU: network interface does not come up after installing open-vm-tools
** Description changed: - FIX: - • Please sync open-vm-tools 2008.11.18-130226-1lenny1 from Lenny into Jaunty; the only difference from the current Jaunty version is this fix. (Done!) - • A debdiff for an Intrepid SRU is posted in bug 302226. + When installing open-vm-tools on Intrepid, the network *immediately* + disconnects itself and no longer comes up on boot, because the + initscript unloads the pcnet32 driver in order to try to replace it with + the vmxnet driver. + + This has been fixed in Jaunty by syncing 2008.11.18-130226-1lenny1. The attached debdiff (comment 24) includes the three relevant Git commits from the Debian repository: + * Updating initscript to correctly handle vmxnet (Closes: #479090, #488810). + * Correcting typo in dh_installinit call. + * Always prefering vmxnet over pcnet32 through modprobe and initramfs configuration (Closes: #502365). + The effect of these changes is that vmxnet will be loaded instead of pcnet32 at boot, and pcnet32 will never be unloaded while the system is running. + + This debdiff also fixes bug #306835 “vmware-guestd crashing” and bug + #302226 “vmware-user doesn't autostart”, and descriptions of the + corresponding patches are posted there. + + The patched package has been in my PPA for four weeks, and confirmed + working by three other users. Risk of regression is low, especially + given that these three bugs essentially prevent the current Intrepid + package from being useful in any way. === Binary package hint: open-vm-tools After installing open-vm-tools, the network will not come up automatically after a reboot. If the kernel modules have not been built yet, the open-vm-tools init script will rmmod the pcnet32 network driver, then try to modprobe vmxnet, and fail, leaving the system without networking. If the kernel modules have been built, the open-vm-tools init script will rmmod the pcnet32 network driver, then try to modprobe vmxnet, which works, but the network doesn't come up. You have to rmmod vmxnet then re-modprobe it, then /etc/init.d/networking restart to bring the network up. Seeing as most vmware guests are server, this is a serious issue, as it prevents automated startups. -- SRU: 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
