It could be a sleep issue. Check the console to see if waking up the VM via a mouse movement has any effect.
I have also seen similar issues that were related to the length of DHCP leases and timesync. IIRC, problems occur if the computer's time sync skew is greater than the DHCP lease duration when the lease is first obtained. Check if the computer's time is synchronized when it first comes up and the initial lease expiration time. I have seen cases where the computer's time eventually gets synchronized and its lease expiration winds up being in the past. The computer then loses it's lease and may not properly obtain a new one. -Andy On Wed, Aug 1, 2012 at 10:51 PM, Marhn Fullmer <[email protected]> wrote: > Hi, > > Win XP probably went into power-saving hibernation. > Try checking Control Panel -> Power Options > & make sure "Always on" is selected. BTW, > > MS is going to stop shipping security patches > for XP in the forsee-able future. I'd make sure > that licensing, security, EOL (End Of Life) & > support was well understood for any Windows, > XP or otherwise. Of course, that applies to any > applications & OS, etc but Windows is definitely > the 800 lb gorilla in many spaces. > > sincerely, > Marhn Fullmer > Manager, COE Networking Laboratories > NCSU Computer Science Dept > > > On Wed, Aug 1, 2012 at 10:35 PM, Peter Dimitrios <[email protected]> wrote: >> We're seeing a problem with some Windows XP VMs...they are preloaded >> and active to VMWare ESXi 4.1, but after about 4 hours VCL can no >> longer ssh into them, and so VCL won't use them to serve reservations >> faster. So far, it looks like something in Windows or VMware is >> closing down all the ports after some period of idleness. We were >> suspecting Windows Firewall, Windows Update or antivirus software >> kicking in, but so far that doesn't seem to be the cause. >> >> We have brought up the same image independent of VCL in another VM, >> and it hasn't had the same issue, so we're wondering if some of the >> post load scripts for WinXP might be setting something to cause this >> "idle image lockout" . Anyone have some breadcrumbs for resolving >> this kind of issue? Could the problem be with some default settings >> for Cygwin sshd under WinXP that VCL isn't overriding? >> >> -Peter Dimitrios, [email protected]
