It remains on the "Starting Windows" screen.  It happens when I perform the 
"Create/Update Image" function and the image is cloned to create the new vm.  
The Windows (System) log doesn't show anything out of the ordinary, although I 
did notice that there is about a 9min delay from the "Kernel-Processor-Power" 
entry and "Service Control Manager" entry.  Details of both entries are listed 

Information  6/13/2011 4:13:25 PM Kernel-Processor-Power: 
Event Properties -Event 26, Kernel-Processor Power 
Processor 0 in group 0 exposes the following: 
1 idle state(s) 
0 performance state(s) 
8 throttle states(s) 

Information 6/13/2011 4:21:56 EventLog: 
Event Properties - Event 6005, EventLog 
The Event Log service was started. 

Any ideas on the issue(s)? 


>>> Andy Kurth <> 06/06/11 10:12 AM >>>
I haven't experienced this.  What is on the console during this time?
Do you see the "Starting Windows" screen.  Does it happen every time
you reboot the VM or only the first time it is powered on?  There may
also be helpful information in the Windows event log.


On Fri, May 27, 2011 at 3:25 PM, Kelly Robinson <> wrote:
> I'm testing a Windows 7 image (on ESXi 4.1) and have experienced extremely
> slow boot times which causes imaging reservations (or reloading) of the
> Windows 7 image to fail due to timeouts.  The vm eventually boots, but it
> takes about 12 minutes for the login screen to appear.  The Windows 7 image
> is configured with 2Gs of memory, 1 CPU and with the LSI Logic Parallel SCSI
> controller.  Are there other values that need to be tweaked?   I was able to
> successfully perform imaging reservations for Windows XP, but Window 7 has
> given us problems.  Has anyone else experienced this issue?
> Kelly
> Georgia State University

Reply via email to