VirtualBox Vagrant guests broken networking after sleep/for a while of inactivity

[beachboy]

I have a Ubuntu 16.04.5 LTS machine running Vagrant 1:2.0.2 and VirtualBox 5.1.38-dfsg-0ubuntu1.16.04.1.

The guest VMs (running Debian GNU/Linux 8.11) seem to have broken networking either after the host sending the automatic powerDown() command or a few hours of inactivity.

Code: Select all

VBox.log.2:00:03:15.361099 ****************** Guest state at power off for VCpu 1 ******************
VBox.log.2:00:03:15.361220 ************** End of Guest state at power off for VCpu 1 ***************
VBox.log.2:00:03:15.361244 ****************** Guest state at power off for VCpu 0 ******************
VBox.log.2:00:03:15.361437 ************** End of Guest state at power off ***************
VBox.log.3:00:05:09.449878 Console::powerDown(): A request to power off the VM has been issued (mMachineState=Stopping, InUninit=0)
VBox.log.3:00:05:09.450134 ****************** Guest state at power off for VCpu 7 ******************
VBox.log.3:00:05:09.450243 ************** End of Guest state at power off for VCpu 7 ***************
VBox.log.3:00:05:09.450260 ****************** Guest state at power off for VCpu 6 ******************
VBox.log.3:00:05:09.450331 ************** End of Guest state at power off for VCpu 6 ***************

WORKING NETWORKING

Code: Select all

vagrant@machine:~$ /sbin/route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         88.99.181.41    0.0.0.0         UG    0      0        0 eth1
10.0.2.0        0.0.0.0         255.255.255.0   U     0      0        0 eth0
88.99.181.40    0.0.0.0         255.255.255.248 U     0      0        0 eth1

machine:~$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=123 time=5.42 ms

BROKEN NETWORKING

Code: Select all

vagrant@machine:~$ /sbin/route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         88.99.181.41    0.0.0.0         UG    0      0        0 eth1
10.0.2.0        0.0.0.0         255.255.255.0   U     0      0        0 eth0
88.99.181.40    0.0.0.0         255.255.255.248 U     0      0        0 eth1

vagrant@machine:~$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.

A simple

vagrant reload machine

brings the VM back online with working networking and no TCP/IP configuration changes.

What do you think could be causing this and what is the appropriate solution?

[socratis]

Vagrant is a program that relies on VirtualBox but modifies its configuration files in unknown ways to us, especially the networking part. It is not supported on these VirtualBox user forums, they have their own Vagrant support channels. If you are having this problem with a standalone version of VirtualBox (after a complete uninstallation of Vagrant), then we can continue this discussion.