Guest can't access host network after resume from hibernation (hybrid sleep).

[hotjava1231]

Host : Windows Server 2008 R2 SP1.
Guest : 64-bit Arch Linux with kernel 4.5.4-1-ARCH.
Network : Bridged with host network card (VirtualBox NDIS6 Bridged Networking Driver).

After resume from hibernation, guest can't access host network. No ping packets reach host. Rebooting guest doesn't help. Only totally powering off and then turning it on helps and guest can access host again.

Maybe related to bug ticket https://www.virtualbox.org/ticket/14457

[hotjava1231]

Reinstalling VirtualBox 5.0.20 with NDIS5 Bridged Networking Driver as instructed here https://www.virtualbox.org/manual/ch02.html (running setup from command line with these options : msiexec /i VirtualBox-<version>-MultiArch_<x86|amd64>.msi NETWORKTYPE=NDIS5) helps. Guest can now access host network after resume from hibernation.

[hotjava1231]

Unfortunately reinstalling with NDIS5 Bridged Networking Driver didn't help much. Although I can now ping host and outer-world (aka Internet), accessing host shares doesn't work like it did in 4.3.12 version of VirtualBox.

Attached logs of problematic guests.

[hotjava1231]

Switched to VirtualBox VM 5.1.3 r109110 test release and using its NDIS6 Bridged Networking Driver. Same problem when resuming from hibernate, no access to other VM's, LAN and the Internet.

[ahr]

The tickets about this issue all seem to be Windows hosts but I have this problem running linux guests in linux hosts. For me, the problem can be worked around by simply changing the address assigned to the vboxnet0 interface. On a Linux host, this is the name of the nic running the host side of the "host only" network. For me, it was set to 192.168.56.1, which is reasonable. Inside my guest, i have eth2 set to 192.168.56.15 and everything works. When I close and reopen my laptop, I get a guest nic that can reach out but the host cannot reach in. I did the following on my host

$ sudo vboxmanage hostonlyif ipconfig vboxnet0 --ip 192.168.56.77
$ sudo vboxmanage hostonlyif ipconfig vboxnet0 --ip 192.168.56.1

thus changing the nic assigned to the host side of the network and immediately changing it back. My Ubuntu Network Manager icon flashed that it had reconnected to that network. My network works fine and the guest did not need to be restarted.

I have added these lines to a file: /etc/pm/suspend.d/fixvboxhonet and made it executable.

Seems to be work around it for me.

[Valery Ushakov]

Replying to ahr:

The tickets about this issue all seem to be Windows hosts but I have this problem running linux guests in linux hosts.

#13873? You don't provide any information about your system, so it's hard to tell.

Anyway, this problem is obviously completely unrelated to the Windows problem described in this bug, so please, don't continue discussing it here. File a new bug if necessary.

[hotjava1231]

And it did happen again. Attached fresh logs.

[L Ecram]

I was wondering if there is any news about this issue.

My host is Win10 build 1803 (incl. latest updates) and the guest I use is Win8.1 (incl. latest updates)

Using VB v5.2.18 now, but the problem also persists in 5.1.30, from which I came.

In the past I used the sleep mode on the host. But this sleep mode seems to be broken after upgrading the host from Win10 build 1703 to 1709. With build 1709 and higher, after resume from sleep: black screen with blinking cursor in the upper left corner. Had several chats with MS, but they don't blame there self....

So I am forced to use hibernate.

Now, when the hosts hibernates, while the guest is running, the guest has no network connection after resuming host from hibernation. The only option to get it to work, is shutting down the guest and restarting it. No need to do more on the host (reboot or so)

Is this 'network loss' now a Windows or a Virtualbox problem?

If I can help to find the root cause, let me know.

[L Ecram]

Update: with v5.2.22, after host resume from hibernate, the guest can access the network.

[L Ecram]

vbox

[L Ecram]

vbox

[L Ecram]

vbox

[L Ecram]

vboxhardening

[L Ecram]

Sorry, was to fast, happend again.

Did some additional test, and see that after the first resume from hibernate, the network interface comes up and running. After a second hibernate/resume, the network interface is down.

Steps performed to reproduce:
-boot host
-start guest VM through virtualbox UI interface
-login to guest, check internet connection (google something)
-hibernate host (first time)
-power on host (i.e. remumes from hibernate) => network available
-hibernate host (second time)
-power on host (i.e. remumes from hibernate) => no network available
-shutdown guest
-start guest VM => network available

Repeated the above steps several times, after the second resume it always fails.

(sorry vbox.2.log/vbox.5.log are the same, attache file while it was uploading...)

Hope this helps to get this fixed.

[msns]

Still happens on VirtualBox 6.1.22 r144080 (Qt5.6.2), host: Windows Version 10.0.19042 Build 19042, Guest: Bitnami Discourse VM (based on Linux), ​link

[MikeKulls]

How is this still an issue in 2022? Is Virtual Box abandonware?

The fix mentioned as the second comment in this thread doesn't work, it results in the VMs not being able to see the host network interfaces at all. It's completely useless.

[MikeKulls2]

I've switched to VMWare Player after years of using VirtualBox, I can confirm it doesn't have this issue so it's not my PC.