Sorry, I dropped the ball on this. Since there was no problem with 14.10, and especially if the problem exists with VMWare as well, it seems likely that the problem is related to systemd in 15.04. I've since discovered that a simple "ifconfig vboxnet0 192.168.10.1" will restore network connectivity to the guest, and have been using that instead of suspending/resuming it. Of course, this depends on what IP was originally configured (I'm using Homestead+Vagrant). It looks like this has already been reported upstream here: https://www.virtualbox.org/ticket/13873
** Bug watch added: Virtualbox Trac #13873 http://www.virtualbox.org/ticket/13873 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1460750 Title: Virtual network (vboxnet0) down after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1460750/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
