virtualbox.org

I just updated to 4.3.22 on Windows 8.1, and my Ubuntu 10.04 guest network restarts very often.

When using an older version 4.3.18 this problem doesn't occur.

Have the same issue. Windows 7 host, debian wheezy guest. Worked fine on the previous version.

I have the same problem since I installed 4.3.22 last week. The network worked perfectly for days and now it keeps going down/up/down/..., which renders my VM mostly useless since it keeps resetting my ssh connections

I'm running a Fedora Core 20 guest on a Win 7 host

I basically repeatedly get the following in dmesg

[Feb16 11:55] e1000: p2p1 NIC Link is Down
[ +4.009127] e1000: p2p1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX

With the following matching messages in /var/log/messages

Feb 16 11:55:03 lsce3017 kernel: [248546.528256] e1000: p2p1 NIC Link is Down
Feb 16 11:55:03 lsce3017 kernel: e1000: p2p1 NIC Link is Down
Feb 16 11:55:03 lsce3017 NetworkManager[432]: <info> (p2p1): link disconnected (deferring action for 4 seconds)
Feb 16 11:55:07 lsce3017 kernel: [248550.537383] e1000: p2p1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Feb 16 11:55:07 lsce3017 kernel: e1000: p2p1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Feb 16 11:55:07 lsce3017 NetworkManager[432]: <info> (p2p1): link connected

I have attached a 4.3.20 and a 4.3.22 log file

Running the VB 4.3.22 install program again and rebooting when prompted did not solve anything (I tried twice)

VBox.log? Bueller? Anyone?

If fixing the problem requires guessing all the relevant details, it does take longer.

Thanks for the logs! That does help.

Probably only Windows hosts and only VMs using NAT are affected.

The same problem. Windows 7 (64) host, Xubuntu 14.04/14.10 (32) guests. Network configured via NAT and connection breaks at least ~every five minutes. Downgraded to 4.3.20 and it works well again.

michaln wrote: Probably only Windows hosts and only VMs using NAT are affected.

I haven't noticed any problem on OSX or Linux hosts.

Lucky me

Can you suggest any workaround? What do you think of That Guy From That Place answer on http://serverfault.com/questions/575571 ... et-adapter or should I go back to 4.3.20 ?

I would like to go back to work, so any basic network setting that will allow me to do an ssh from my VB to a machine outside of my Win 7 host is fine. And I would like my ssh connection to stay up as long as the VM is running, even if it is running several days in a row (this worked perfectly with 4.3.20)

I have uninstalled VB (by selecting the remove option from the VB installer), rebooted my host and reinstalled, and still got the same problem. Strangely, I still got my settings after uninstalling/reinstalling (which was convenient) and VB told me that the latest guest additions were already installed when I tried to install them (which makes me wonder if VB was really uninstalled, unless the GA are installed by default when you install VB)

FWIW, I just tried the 'change adapter HW to something non-intel' as mentioned and it seems
to have done the trick ( I picked whatever was at the top of the list ).

I have Ubuntu 14.04 and the same thing is happening but I've tried all the adapters in the list and nothing solves the problem.
I have attached the log file.

I have just used the first non intel adapter as well instead of the default I had (that had been working perfectly with several versions of VB, prior to 4.3.22) and the network has been running smoothly ever since (for 1h25 mn at least)

I have also attached the new log file, that somebody can probably compare with the 4.3.22 log I posted yesterday

BTW, does it matter what adapter we use (as long as it's non Intel in that case)? Can we have some performance issue? I don't have time to check if I also have problems with the other Intel adapters available

We found the cause... turned out that some cases of DHCP lease renewal on the host triggered the link flap for the VM, which was meant to happen only if anything related to DNS configuration actually changed (to maintain network connectivity when the host switches to a different network, e.g. when using a VPN or moving between work and home). This definitely happened only on Windows host, no other host OSes were affected.

For an immediate fix, please pick up the latest Windows test build from https://www.virtualbox.org/wiki/Testbuilds

Note: no need to update the guest additions or the extension pack, the vanilla 4.3.22 do the job nicely. Oh, and if you switched to the PCNet card, don't forget to switch back to the appropriate E1000 variant supported by the guest OS.

Thanks Klaus!

I will wait for the next stable release

The test builds are expected to be stable. They're only small modifications relative to the maintenance releases, and you can update without trouble afterwards once 4.3.24 is out.

klaus, am wondering if issue you outline in your 20-Feb-2015 reply above may explain my issue...

Am running Win7ProSP1 on both host and guest of VBox v.4.3.20. Guest network config'ed for NAT adapter. Guest installed with Juniper Network Connect v.8.0 to VPN to company network. VPN session does successfully connect initially no problem, but after short period of time (sometimes as short as 10-15min up to maybe hour or so) the VPN session inexplicably and consistently drops (though the Juniper client still shows the session connected)

Initially had aforementioned setup with VBox v.4.3.6 running no problem with no such VPN issue. Had since been recommended to upgrade VBox to attempt to resolve different unrelated VBox issue.

Would aforementioned DHCP issue outlined explain my VPN issue or is this likely unrelated?