Debian Guest reset network adapter ignores configuration on VirtualBox after snapshot restore

I'm using virtualbox 5.2 as host and Debian 9 as guest on Ubuntu 14.04.

I have configured my Debian guest system to have a static IP (192.168.56.101) with a host-only adapter (192.168.56.1/24) and no dhcp.

This config will be written to the /etc/network/interfaces.d/setupguest and works perfectly when the machine is booted regularly. The host can ping the guest, and the guest can ping the host.

However, if I take a snapshot and restore that snapshot later, the adapter is reset and the configuration is ignored. The host cannot ping the computer, and the machine cannot ping the host. A /etc/init.d/network restartsolution to the problem. So it can't be the adapter or the host, it has to be a problem on the client.

The reset itself is not the main problem, but blatant disregard for the configuration is the problem after the reset. I can wait a few seconds, but I can't manually log into the machine because it's unattended in production.

How to enforce network profile compliance after adapter reset?

dmesgThe only relevant entry on the guest is:

[...] pcnet32 0000:00:03.0 enp0s3: link down
[...] pcnet32 0000:00:03.0 enp0s3: link up, 100Mbps, full-duplex

While trying to find dirty cronjob hacks, I came across /var/logs/cron.logthis entry at :

..... debian systemd-timesyncd[297]: Network configuration changed, trying to establish connection