Page 1 of 1

Host-only network hang

Posted: 27. Jan 2014, 13:06
by ctoni69
Hi all,

configuration:
laptop macbook pro retina (late 2013)
OS Mavericks 10.9.1
virtualbox VirtualBox 4.3.6
Vm guests Oracle Enterprise Linux 6.5 or Solaris 11.1 doesn't matter, my problem is the same.
Each vmguests has configured a Host Only Adapter.


I have noticed that after a random time, if I open a ssh connection towards my VMguests, network become slow and than hang for short or long time.
$ ping 192.168.2.4
64 bytes from 192.168.2.40: icmp_seq=403 ttl=64 time=0.325 ms
64 bytes from 192.168.2.40: icmp_seq=404 ttl=64 time=0.351 ms
.....................
.....................
64 bytes from 192.168.2.40: icmp_seq=418 ttl=64 time=0.322 ms
64 bytes from 192.168.2.40: icmp_seq=419 ttl=64 time=0.292 ms
64 bytes from 192.168.2.40: icmp_seq=420 ttl=64 time=9078.306 ms
64 bytes from 192.168.2.40: icmp_seq=421 ttl=64 time=8077.124 ms
64 bytes from 192.168.2.40: icmp_seq=422 ttl=64 time=7077.044 ms
64 bytes from 192.168.2.40: icmp_seq=423 ttl=64 time=6075.862 ms
64 bytes from 192.168.2.40: icmp_seq=424 ttl=64 time=5074.871 ms
64 bytes from 192.168.2.40: icmp_seq=425 ttl=64 time=4074.467 ms
64 bytes from 192.168.2.40: icmp_seq=426 ttl=64 time=3074.047 ms
64 bytes from 192.168.2.40: icmp_seq=427 ttl=64 time=2073.402 ms
64 bytes from 192.168.2.40: icmp_seq=428 ttl=64 time=1073.235 ms
64 bytes from 192.168.2.40: icmp_seq=429 ttl=64 time=72.101 ms
64 bytes from 192.168.2.40: icmp_seq=430 ttl=64 time=9170.950 ms
64 bytes from 192.168.2.40: icmp_seq=431 ttl=64 time=8170.069 ms
64 bytes from 192.168.2.40: icmp_seq=432 ttl=64 time=7169.932 ms
64 bytes from 192.168.2.40: icmp_seq=433 ttl=64 time=6168.784 ms
64 bytes from 192.168.2.40: icmp_seq=434 ttl=64 time=5168.331 ms
64 bytes from 192.168.2.40: icmp_seq=435 ttl=64 time=4167.125 ms
64 bytes from 192.168.2.40: icmp_seq=436 ttl=64 time=3165.967 ms
64 bytes from 192.168.2.40: icmp_seq=437 ttl=64 time=2164.710 ms
64 bytes from 192.168.2.40: icmp_seq=438 ttl=64 time=1163.617 ms
64 bytes from 192.168.2.40: icmp_seq=439 ttl=64 time=163.475 ms
64 bytes from 192.168.2.40: icmp_seq=440 ttl=64 time=0.349 ms
................
..............
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
ping: sendto: No route to host
Request timeout for icmp_seq 4
ping: sendto: Host is down
Request timeout for icmp_seq 5
ping: sendto: Host is down
Request timeout for icmp_seq 6
ping: sendto: Host is down
......


Someone has the same issue? Workaround ??

Thanks
Cristiano

Re: Host-only network hang

Posted: 27. Jan 2014, 17:51
by robocoder
Seen it. IIRC it coincides with network changes on the host OS, e.g., when a VPN connection times out and disconnects.

--
Retina, 13-inch, Late 2013, MacOSX 10.9.1

Re: Host-only network hang

Posted: 28. Jan 2014, 03:01
by ctoni69
Hi,
this issue is present also if I restart my laptop without network device actives (no wifi, no ethernet adapter insert).

No vpn configuration present.

Regards
Cristiano

Re: Host-only network hang

Posted: 28. Jan 2014, 08:38
by socratis
ctoni69 wrote:Each vmguests has configured a Host Only Adapter...
$ ping 192.168.2.4 ...
this issue is present also if I restart my laptop without network device actives (no wifi, no ethernet adapter insert)
Have you tweaked your host-only network? Because the address that you ping is not the "default" for a host-only network, it seems more like a Bridged one. Can you re-check please? Even better, can you post a log of a machine (from boot up to normal shutdown) that exhibits this problem?

Re: Host-only network hang

Posted: 28. Jan 2014, 13:53
by ctoni69
yes I have changed it. I don't see any problem here.

I have attached the logs of 2 vmguest and also a simple ping test between host and vmguests

Regards
Cristiano

Re: Host-only network hang

Posted: 29. Jan 2014, 02:09
by ctoni69
New update,...

if the vmguests are started as:

$ VBosHeadless -s nome

Network is running perfectly without problems.

Cristiano

Re: Host-only network hang

Posted: 1. Feb 2014, 18:20
by noteirak
Reproduce the problem then provide the VM log file, the guest settings, and the output of the following commands on the host :

Code: Select all

vboxmanage list hostonlyifs
vboxmanage list bridgedifs
Then on the host & guest - you might need to find the equivalent command on the system, or use sudo :

Code: Select all

ifconfig -a
route -n