-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Maybe it's just a windows thing. They came out with a hotfix for it
anyway.
Fix Windows 7 SP1 Slow Startup Due to Large Number of Restore Points
http://news.softpedia.com/news/Fix-Windows-7-SP1-Slow-Startup-Due-to-Large-Number-of-Restore-Points-217883.shtml
“This issue occurs because the boot plan for the ReadyBoot feature exceeds
the size limit of 512 kilobytes (KB). Each restore point creates a snapshot
of Windows that Volsnap.sys must validate during the startup process,”
Microsoft explained.
But it doesn't explain why sometimes its fast and sometimes it's slow.
Maybe disabling ReadyBoot would help?
On 9/22/2011 1:48 PM, Waldron, Michael H wrote:
James,
Thanks for the suggestions. I've already increased the ssh timeout, however
this hang goes way beyond a reasonable amount of time, anywhere from 20-30
minutes.
I'll test with your dhcp suggestion. Although again, my Win7 images that
haven't been updated to SP1 are booting just fine, so I'm trying to figure
what got changed in the OS with the SP1 update that's causing this. One time
it might only spend 30 seconds at the Windows Starting screen, the next it
might be 10 minutes.
Mike Waldron
Systems Specialist
ITS Research Computing
University of North Carolina at Chapel Hill
CB #3420, ITS Manning, Rm 2509
919-962-9778
From: James O'Dell [jod...@fullerton.edu]
Sent: Thursday, September 22, 2011 3:36 PM
To: vcl-user@incubator.apache.org
Subject: Re: Windows 7 SP1 boot hangs
I've got the same setup, and run into what looks to be the same
problem. ( Win7 booting taking so long that the ssh connection
times out )
I've done a couple things, and it seems to have gotten better.
1) adjust the ssh timeout from 5 to 10 minutes
/opt/vcl/lib/VCL/Module/OS.pm
'$ssh_response_timeout_seconds = 1200;'
Why is this hard coded anyway?
2) Turn off the WINS, and the netbios-over-tcp using settings in
the dhcp server to prevent the booting system from registering
with a WINS server, and from using NBoT.
shared-network VCLGuestRDPnetwork {
...
option netbios-name-servers noip;
if substring ( option vendor-class-identifier, 0, 8 ) = MSFT 5.0 {
vendor-option-space MSFT;
# 1 = enable, 2 = disable - NetBIOS over TCP/IP:
option MSFT.nbt 2;
}
...
}
'noip' does not resolve to anything. Which causes dhcp to clear the
'netbios-name-servers' (aka WINS) setting if it is globally set.
Maybe this will help
__Jim
On 9/22/2011 11:53 AM, Waldron, Michael H wrote:
I've been running Windows 7 images on ESXi 4.1 hosts in our VCL without
problem. When I updated several of those Windows 7 images to service
pack 1, I'm seeing an issue where more times than not, the VM will hang
at the Windows Starting screen for up to 30 minutes. If I revert back to
the pre-SP1 image, it boots just fine.
What's maddening is that it's not consistent. Some times it will boot
normally, but many times there's this long hang while booting, which of
course causes the reservation to fail. This happens across different VMs
running on different ESXi hosts. The common factor is Windows 7 SP1.
Has anyone else seen this?
Mike Waldron
Systems Specialist
ITS Research Computing
University of North Carolina at Chapel Hill
CB #3420, ITS Manning, Rm 2509
919-962-9778
- --
Jim O'Dell
Network Analyst
California State University Fullerton
Email: jod...@fullerton.edu
Phone: (657) 278-2256
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk57rdQACgkQREVHAOnXPYQtTwCdEQk+EuR/yhumZZhhJwjcqj7q
G+gAoJdw7DKZSwf7AMBMwboyguDiSfQh
=oJeV
-END PGP SIGNATURE-
