Host-only adapter fails after sleep-wake transition

[Jeff Morgenthaler]

In 5.0.2, Window 7 host, Debian 8 guest, the host-only adapter only works after a full restart of host and guest. Once you put the host to sleep and wake it back up again, the host-only adapter is broken. Here is what ping from the guest gives:

root@byted> ping 192.168.56.1 PING 192.168.56.1 (192.168.56.1) 56(84) bytes of data. From 192.168.56.101 icmp_seq=1 Destination Host Unreachable

where 192.168.56.101 is the guest IP and 192.168.56.1 is the adapter IP. There is a similar break in ping of guest IP from host.

jpm

[jpoot]

I am experiencing the same problem using Windows 8.1 host, Oracle Linux 6 & 7 guest. Stop VB, Disable/enable the adapter and start VB helps most of the time.

[GabeF]

I notice this same issue as recent as 5.0.6 on Windows 7 host.

Same problem even though I installed with NDIS5 network driver.

VirtualBox-5.0.6-103037-Win.exe -msiparams NETWORKTYPE=NDIS5

My host is a pretty complicated setup, with vmware, Juniper Pulse VPN, and Symantec AV.

[fmagni]

Same problem here on 5.0.2.

It was working before I upgrade from 4.3.24

[gvoima]

I also get this same problem and it's quite frustrating. I have a host-only network adapter that I use for ssh and apache and after I updated from 4.3.x to 5.0.10 the host-only stops working after sleep.

I have Win7 host and Debian 8 guest.

If I turn the VM off and disable/enable the host-only interface, it doesn't help. I have to make a full reboot.

Is there any logs or debugging I could make to get this issue forward? I'd rather use VirtualBox 5.0.x just because of the detachable start functionality and paravirtualization.

[Todd]

This is happening to me, but with bridged networking on Windows 7 host (x64 sp1) with Windows 8.1 guest, and VirtualBox 5.0.10. My settings:

• PAE/nx: enabled
• paravirtualization method: Hyper-V
• VT-x and nested paging: enabled
• networking: bridged using host's wireless adapter (Intel n 6205) and masquerading as Intel PRO/1000 MT on the guest

[adamo102]

Happens with newest 5.0.14 as well. Just noticed that occasionally I am getting message from host (windows) about ip address conflict.

Other then reboot I can also remove the HostOnly adapter in the VirtualBox preferences and add new one with different IP.

[adrianofnatal]

Facing the same problem here with Windows 10 and VirtualBox 5.0.14 r105127. The guest system was creating using default parameters.

It only works with a full restart (host and guest), and sometimes the host-only IP changes when restart.

One thing that I noticed is that when return from hibernation or sleep, the host don't ping the address associated with host-only interface. I disable and enable the host-only and ping works, but guest system won't be able to communicate with it. The ICP protocol is allowed in Windows Firewall for all interfaces.

[Kahli]

Same problem here with 5.0.14 and downgraded 5.0.10 on Windows 7. Interesting point is that I'm pretty sure it worked with 5.0.14 and Windows 7 until a few days ago. Can't exactly name what changed. Thought about the only performed Windows Update ​https://support.microsoft.com/de-de/kb/3102429 which makes no sense. But what about a Python Update from 2.7.8 to 2.7.11?

[Horden]

Having the same problem with Windows 7 and 5.0.14 It gets really frustrating, so far I can only solve the issue by restarting the host.

[Amir Barkal]

Same problem here with Windows 8.1 Pro + VirtualBox 5.0.16 r105871.

The only way to solve this after sleep \ hibernate is to create a new Host-Only network adapter and assign it the the vm. The old adapter becomes completely unusable.

Please escalate this issue to level "critical". I've attached VBoxSVC.log with events right after resuming host from sleep.

Thanks

UPDATE #1 After creating a new Host-Only network adapter from VirtualBox network settings, I've decided to test the behavior when the built in dhcp server is disabled. The results seems to be different, and after the host goes to sleep and wakes up - the host-only adapter is still functioning. So a workaround to this issue could to simply disable the DHCP server of VirtualBox

[zzxt]

Same problem here with Windows 10 Pro + VirtualBox 5.0.16 CentOs7 guest

[miyakawataku]

Same problem.

• Host: Windows 10 Pro x64
• VirtualBox: 5.0.18 r106667, DHCP service for Host-only network is disabled
• Guest: Ubuntu 14.04 x64.

After wakeup from the host sleep, I can ping the virtual NIC on the host side, but cannot ping the guest.

The only solution is host reboot. Logout+login to the host does not work.

[gvoima]

Replying to amirb:

UPDATE #1 After creating a new Host-Only network adapter from VirtualBox network settings, I've decided to test the behavior when the built in dhcp server is disabled. The results seems to be different, and after the host goes to sleep and wakes up - the host-only adapter is still functioning. So a workaround to this issue could to simply disable the DHCP server of VirtualBox

Has anyone else tested this "fix" and got the same results? I have quite a big environment which I need quite frequently and would not want to do the install/reinstall rigmarole all over again. If this really works, it would be a great workaround.

[gvoima]

Replying to gvoima:

Replying to amirb:

UPDATE #1 After creating a new Host-Only network adapter from VirtualBox network settings, I've decided to test the behavior when the built in dhcp server is disabled. The results seems to be different, and after the host goes to sleep and wakes up - the host-only adapter is still functioning. So a workaround to this issue could to simply disable the DHCP server of VirtualBox

Has anyone else tested this "fix" and got the same results? I have quite a big environment which I need quite frequently and would not want to do the install/reinstall rigmarole all over again. If this really works, it would be a great workaround.

I had some time to test this theory, and no, it doesn't help to disable DHCP. The adapter fails either way after suspend, with or without DHCP.

[Daniel Miller]

Though one other person mentioned a Windows guest, I wanted to make sure it was pointed out. This bug is not confined to Linux guests.

Also, I have been able to occasionally resolve the issue without a reboot of the host. I close the client, as well as the VirtualBox Manager, watch my system processes until all VBoxNetDHCP.exe, VBoxSVC.exe, and VirtualBox.exe instances have stopped. I disabled and re-enabled the VirtualBox Host-Only Network adapter as well for good measure. Then starting VirtualBox Manager up again and re launching a VM allowed my host to once again ping the guest.

[da4an1qu1]

I keep upgrading from 4.3.38 to any of the 5 versions in forlorn hope that this bug is fixed. And as of 5.1.6, still I have found it isn't. So I keep downgrading. But 4.3.38 has its own problems with the NAT interfaces. They freeze up completely at random points. More so with the virtio NIC, but even with Fast III.

My only hope of a reliable VirtualBox is that this bug gets fixed. If I'm ever able to, I'll try and devote some time of my own to investigate...

[Jeff Morgenthaler]

Seems to be fixed! Current system is Windows 10 host, VirtualBox 5.1.6, Debian 8 guest. Using Cygwin X on Windows 10 to establish connections to guest via localhost (port forwarded to guest) and host only network, both stay open and functional through sleep-wake transition. Thanks!

jpm

[janxb]

Can't confirm the comment from jpmorgen. I am still having trouble after hibernation, my host-only adapter does not work until a reboot. Tested on Windows with VirtualBox 5.1.10.

The host-only adapter loses its IP address configuration after hibernation. Disabling and re-enabling the adapter on the host gives the IP address back, but connection still doesn't work.

Edit: Can confirm the temporary solution from Daniel Miller, after closing every VM and the Manager, I was able to restart the adapter and ping my VM.

[yarilc]

Same issue here with 5.1.10 on Windows 7. After killing all the Virtualbox processes I was able to reach my guests host again through the host-only adapter

[pFa]

Hi,

Same problem as jpmorgen

• VB=5.1.26
• host=ms-windows 10 home, nic=Realtek PCIe GBE Family Controller
• guest=debian 9, 2 nics = NAT + Host-Only network

NAT works like a charm.
I wrote a small script (VM name is location.deb9)

@rem ---------------------------------------------------------------------------
@rem  Script used to reset VirtualBox Host Only Network from a ms-windows host
@rem ---------------------------------------------------------------------------
@set myPath=C:\Program Files\Oracle\VirtualBox\
@rem ---- 1) Save all the VMs state
"%myPath%VBoxManage.exe" controlvm location.deb9 savestate
@timeout /T 5 /NOBREAK
@rem ---- 2) Kill some stuff
taskkill /T /F /IM VirtualBox.exe
@timeout /T 5 /NOBREAK
taskkill /T /F /IM VBoxSVC.exe
@rem ---- 3) Display the Net connections panel
control netconnections
pause Disable then enable VirtualBox Host-Only Network #n
@rem 5) Start the VMs
"%myPath%VBoxManage.exe" startvm location.deb9
@timeout /T 5 /NOBREAK
"%myPath%VBoxManage.exe" controlvm location.deb9 setlinkstate2 off
@timeout /T 15 /NOBREAK
"%myPath%VBoxManage.exe" controlvm location.deb9 setlinkstate2 on
@timeout /T 30 /NOBREAK
"%myPath%VBoxManage.exe" controlvm location.deb9 setlinkstate2 off
@timeout /T 1 /NOBREAK
"%myPath%VBoxManage.exe" controlvm location.deb9 setlinkstate2 on
@timeout /T 15 /NOBREAK

In short,

• save the VM state
• kill remaining VBox process
• launch a network panel and wait...
• ... manually disable then enable the "VirtualBox Host-Only Network"
• start the VM
• and set the link-state of the corresponding nic (mine is # 2, hence setlinkstate2) alternatively off then on, twice.

Hope That Helps.

See also 3625 guest lose network connectivity after host resumes from sleep - although the host was a Linux machine, 8 years ago.

[astrlsrfr]

Same issue.. in bridged mode. Have had it for a long time. At least as long as this tick has been open. I live and breath hibernation with remote WoLs, so it's made me use VB less, unfortunately.

VB:  5.1.28
Host: Win7 Ultimate
Guest:  Debian 8
NIC:  Realtek PCIe GBE Family Controller

pFa, your script worked for me, thx. Prolly a bout as good a solution as one can hope for for the forseeable...

[kurtisc]

Still an issue for bridged adapter. Solving with closing and opening the guest, for now.

-Host: Windows 10 Pro x64 v1709 Build 16299.371

-VirtualBox: 5.2.8 r121009 (Qt5.6.2)

-Guest: Ubuntu 16.04 LTS x64 (xenial)

[RoryGS]

Still a issue for me with host and or bridge adapter. Current workaround is saving the guest state and opening again for now, what a waste of time and a pain for dev process.

• Host: Windows 10 Pro x64 - OS build 17134.165

• VirtualBox: Version 5.2.12 r122591 (Qt5.6.2) - defaults

• Guest: Freshly installed minimal - CentOS Linux release 7.5.1804 (Core) (Other versions of CentOS 7 also)

Is this bug being looked into? Its easily to replicate I would assume with a newly installed CentOS 7 and I assume other guests.

Thanks Rory

[filimonov]

duplicate/related #14374 ?