virtualbox.org

I followed instructions on this blog http://edstevensdba.wordpress.com/2012/ ... network-2/ and pretty much everything is working fine but not this one ...

If i have a running putty connection and if I put my laptop in hybernate/sleep by putting down laptop screen off , any existing active putty session becomes inactive if i start my laptop after sometime/few hours.. is this a know behavior in VM ?

Here’s my O/S version & i am doing ssh

Linux pr.localhosts.localdomain 2.6.32-400.29.1.el5uek #1 SMP Tue Jun 11 15:17:29 PDT 2013 i686 i686 i386 GNU/Linux

Let me know if you need any additional information.

-Learner

Many of my Putty/SSH session become inactive if I do nothing for a few hours, even if I don't use Vbox.
I think it is more a "problem" of SSH session timeout instead of a Virtualbox problem.

Your laptop is going to sleep, and the VM is paused, and this is leading putty to loose the connection. That's not a virtualbox problem but the fact that you put to sleep/hypernate your computer.
network stack will be reset, and so you'll loose your connection. That would happen with any connection you would leave open.

I agree with your comments, the reason why i was not so sure was because few weeks back it never use to happen, after i installed few more rpm on OL it started happening... so thought of checking here. Anyways thanks for the help n info.

One more small question ...

Currently when i put my laptop screen off which obviously puts my laptop to hyberante mode and when i start it back , if i take a NEW putty , it takes almost 15-20 seconds to bring prompt to enter user id. If i go inside virtual box and restart both eth0 n eth1 via network manager , and then try again to take connection via putty it works fine without any 15-20 sec delay. Are you aware of this sort of a issue … i can get the connection , it’s those wait for 15-20 sec everytime is painful.

-Learner

That would be a guest OS issue, timing out on a DNS lookup most likely, again due to the network reset stack (which the Guest OS is not aware of).

noteirak wrote:That would be a guest OS issue, timing out on a DNS lookup most likely, again due to the network reset stack (which the Guest OS is not aware of).

Is this solvable ? Can you provide some pointers ?

AFAIK no... it's a feature of the OS itself... you would have to look into it but I highly doubt it.

noteirak wrote:AFAIK no... it's a feature of the OS itself... you would have to look into it but I highly doubt it.

Thanks for the update.