FYI, I looked into VMware's Customization.pm file and their comment says that says they run "/sbin/ifconfig eth0 2> /dev/null" to "wake up" the interface, so whatever's going wrong isn't as simple as a hardcoded network interface address in VMware code.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1782451 Title: open-vm-tools 2:10.2.0-3~ubuntu0.16.04.1 customization doesn't work with predictable network interface names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1782451/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
