try reducing your vCPU count to maybe 1 or 2 to see if that fixes it.
What is the VM used for? Has analysis of the performance figures been carried out? Have you spec'd the virtual machine according to this? In most enviorments you will fine 1vCPU is enough and 2 in worst case scenarios. It would be very rare that 4 would be required.
What is the current memory usage on your host, are you currently over commiting memory at all?
Can't say I have experienced any slow reboots with the VM's at our site or our customers for anything other than software delays.
www.virtualisedreality.com | www.twitter.com/virtualisedreal
What kind of applications are you running for this 4 vCPU guest? It seems like you are overallocated unncessary virtual CPUs for that VMs, in theories, if you understand resource management from ESX, you wouldn't want to use 4 vCPU unless it really uses it all but most of the time it will create a performance bottleneck. As recommended, change it to 2 vCPU if its Exchange, Oracle, SQL boxes. You should check out resource management guide for details
If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!
Regards,
Stefan Nguyen
VMware vExpert 2009
iGeek Systems Inc.
VMware, Citrix, Microsoft Consultant
These servers are currently being built for Exchange 2007 backend servers. So they require this type of resources..
Hi,
Did you set memory reservations on those VMs? If so how much?
If you do not set a memory reservation, then during boot time, the hypervisor will create a swap file as big as the memory that the VM has, so for an 8GB VM, it will create a 8GB swap file on disk and this might take a little while.
By setting a reservation, the size of the reservation is removed from the size of the vmkernel swap file.
So for example by setting a 5GB memory reservation, only a 3GB swap file is being created.
See also:
http://www.van-lieshout.com/2009/04/esx-memory-management-part-1/
--
Wil
_____________________________________________________
Visit the VMware developers wiki at http://www.vi-toolkit.com
I've tried that and are still seeing the slow reboot.. Took 10mins so far and still waiting with the memory reservation in place.
Well after speaking to a SR from Vmware it looks to be a bug in ESX 3.5 Update 4 that has been corrected in vSphere 4