we are currently experiencing a problem where new machines that are being provisioned are taking a long time
it is currently taking 23mins which i belive it shouldent be. the longest part seems to be the customizing stage.
the vm seems to sit there at the logon screen for about 10-15min then eventually reboot and become available.
wtching the vspere client events it
clones the replica
adds a tag (2sec)
then there are a couple of reconfigure vm (50sec)
then powers on the vm (1sec)
then a couple of resource allocation changes (2min)
then the next thing is a message from the host 17 min later saying
Message from
hostname: The VMware Tools package is not running in this virtual machine. The package might be necessary for the guest operating system to run at resolutions higher than 640x480 with 16 colors.
The package provides significant performance benefits as well. To install it, choose VM > Install VMware Tools… after the guest operating system starts. VMware ESX can remind you to install the
VMware Tools package when you power on the VM. Select OK to enable the reminder.
then it reconfigures the vm a couple more times (1min)
reboots(1min)
couple resource allocation changes (1min)
then its ready to go.
so it looks like something is not happy with vmware tools but once the machine is up and running it says that vmware tools is running and current.
had a look in the composer logs and in the these were all that were there for the time on the machine being provisions and they just so happened to be in the 17 min window.
2014-01-10 08:18:59,446 [1400] INFO CSvmGaService - [svmGaService.cpp, 87] Initialized the Service
2014-01-10 08:18:59,461 [1400] INFO CustomizationPersistentInfoReg - [CustomizationPersistentInfoReg.cpp, 98] Opened guest registry key for accessing customization info.
2014-01-10 08:18:59,461 [1400] DEBUG CSvmGaService - [svmGaService.cpp, 323] In RunService
2014-01-10 08:19:00,538 [1400] INFO CSvmGaService - [svmGaService.cpp, 295] No Policy or SVM disks found
2014-01-10 08:19:00,538 [1400] INFO CSvmGaService - [svmGaService.cpp, 347] In the master VM
2014-01-10 08:19:00,538 [1400] INFO CSvmGaService - [svmGaService.cpp, 411] Service is in state: 4
2014-01-10 08:19:00,538 [1400] DEBUG WaitableManagerWin32 - [WaitableManagerWin32.cpp, 87] Updating callback for event SviServiceStopEvent (00000158)
2014-01-10 08:19:00,538 [1400] DEBUG WaitableManagerWin32 - [WaitableManagerWin32.cpp, 90] adding callback for event SviServiceStopEvent (00000158)
2014-01-10 08:19:00,538 [1400] DEBUG WaitableManagerWin32 - [WaitableManagerWin32.cpp, 179] Dispatching callback for event WaitableManagerInternal (00000150)
2014-01-10 08:19:10,007 [1320] INFO CSvmGaService - [svmGaService.cpp, 442] user logon.
2014-01-10 08:20:53,589 [1320] INFO CSvmGaService - [svmGaService.cpp, 448] user logoff.
2014-01-10 08:20:55,663 [1400] DEBUG WaitableManagerWin32 - [WaitableManagerWin32.cpp, 179] Dispatching callback for event SviServiceStopEvent (00000158)
2014-01-10 08:20:55,663 [1400] INFO CSvmGaService - [svmGaService.cpp, 391] CSvmGaService::RunService: Stop requested.
2014-01-10 08:20:55,663 [1400] INFO CSvmGaService - [svmGaService.cpp, 482] Shutting down the service
2014-01-10 08:20:55,663 [1400] INFO CSvmGaService - [svmGaService.cpp, 487] Stopped the SVM state machine
2014-01-10 08:21:44,853 [1440] INFO CSvmGaService - [svmGaService.cpp, 87] Initialized the Service
2014-01-10 08:21:44,868 [1440] INFO CustomizationPersistentInfoReg - [CustomizationPersistentInfoReg.cpp, 98] Opened guest registry key for accessing customization info.
2014-01-10 08:21:44,868 [1440] DEBUG CSvmGaService - [svmGaService.cpp, 323] In RunService
2014-01-10 08:21:45,945 [1440] INFO CSvmGaService - [svmGaService.cpp, 295] No Policy or SVM disks found
2014-01-10 08:21:45,945 [1440] INFO CSvmGaService - [svmGaService.cpp, 347] In the master VM
2014-01-10 08:21:45,945 [1440] INFO CSvmGaService - [svmGaService.cpp, 411] Service is in state: 4
2014-01-10 08:21:45,945 [1440] DEBUG WaitableManagerWin32 - [WaitableManagerWin32.cpp, 87] Updating callback for event SviServiceStopEvent (00000158)
2014-01-10 08:21:45,945 [1440] DEBUG WaitableManagerWin32 - [WaitableManagerWin32.cpp, 90] adding callback for event SviServiceStopEvent (00000158)
2014-01-10 08:21:45,945 [1440] DEBUG WaitableManagerWin32 - [WaitableManagerWin32.cpp, 179] Dispatching callback for event WaitableManagerInternal (00000150)
2014-01-10 08:21:54,728 [1332] INFO CSvmGaService - [svmGaService.cpp, 442] user logon.
2014-01-10 08:23:58,386 [1332] INFO CSvmGaService - [svmGaService.cpp, 448] user logoff.
Anyone have any ideas on where to start looking.
oh we are running view 5.2 and its a floating pool.