Virtual network (vboxnet0) down after resume from suspend

[hackel]

Since upgrading to Ubuntu 15.04, whenever I suspend my machine with a running Virtualbox instance, upon resuming, I no longer have access to the virtual network interface vboxnet0. The VM itself is still running and I can access it through mapped ports on localhost. If I suspend and resume the VM, the network comes back up fine. Also, within Virtualbox, if I reconfigure the network as described here (https://askubuntu.com/questions/626741/ubuntu-15-04-disconnects-from-virtual-networks-after-wakeup) it comes right back up. I originally noticed this running the 4.3.28 package from virtualbox.org, but have since switched to the Ubuntu/Debian package 4.3.26-dfsg-2ubuntu2 and experience the same issue.

[Gianfranco Costamagna (costamagnagianfranco)]

can you please report it upstream?

https://www.virtualbox.org/ticket/

this is likely an upstream issue,

thanks

[Gianfranco Costamagna (costamagnagianfranco)]

https://www.virtualbox.org/newticket
corrected link.

[Christian Bayer (christian-bay)]

Happens to me too. Worked fine until upgrade to 15.04. I'm on Kubuntu, VirtualBox 4.3.26_Ubuntu. The vboxnet0 device doesn't show up in NetworkManager after resume. However, once I restart the VM or save and resume it, the vboxnet0 device reappears. What is odd, though: For each resume there will be a new vboxnet0 device in NetworkManager (after VirtualBox restored networking).
hackel , did you ever file a ticket with upstream?

[Christian Bayer (christian-bay)]

BTW since that other post suggests it is the same for VirtualBox and VMWare, I doubt this is a bug with upstream.

[hackel (hackel)]

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

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Constantin Gavrilescu (costin-x)]

The vboxnet is down for me too on suspend, and also when undocking my laptop, which triggers unplugging the ethernet wire. After undocking, my ethernet networks is down, along with the vboxnet* interfaces:

$ ip l

4: vboxnet0: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000
    link/ether 0a:00:27:00:00:00 brd ff:ff:ff:ff:ff:ff
5: vboxnet1: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000
    link/ether 0a:00:27:00:00:01 brd ff:ff:ff:ff:ff:ff

$ip a
4: vboxnet0: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
    link/ether 0a:00:27:00:00:00 brd ff:ff:ff:ff:ff:ff
5: vboxnet1: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
    link/ether 0a:00:27:00:00:01 brd ff:ff:ff:ff:ff:ff

[Ibrahim Awwal (ibrahim-awwal)]

There's an upstream issue thread, and a workaround is here: https://www.virtualbox.org/ticket/13873#comment:17

But the issue is apparently actually a NetworkManager issue, so this should possibly be cross posted or moved? Not sure how to do that, but just wanted to post here so that others can find the fix more easily.