which mvn rpm -qf /usr/bin/mvn yum provides maven
RTO（Recovery Time Objective）
RPO（Recovery Point Objective）
Run esxtop on the host where you start it up and look for high ready times on cpu, disk latencies for storage, or memory limits. Or check these values on the performance tab in vCenter – I prefer esxtop – it samples 4x as often by default and you can adjust the sample rate. Check vm properties in vClient as well as .vmx to make sure you do not have any limits set for this vm.
Are these hosts all part of the same cluster?
Do you use resource pools?
Have you checked the logs on your host (var/log/… vmkernel, vmkwarning, as well as the vmware.log in the vm directory) ?
What about the VM’s swap file? If the creation of that is slow, then the VM may take a long time to boot as well. Check to see where that is stored.
Compare all of this VM’s settings to another VM that is not experiencing the problem.
Does this happen with only 1 VM, a specific group of VM’s, or all of them? Does the slow boot vary across different VM types (cpus, memory, storage location, OS)?
How many disks does this VM have? To power on the VM, the host has to write a lock entry on each lun the VM has disks on. Normally this takes a (1-2) MS, but if there is contention for lun meta updates (VMotions, VM power on, VM creation, snapshots growing) then this could delay the boot as well.
What is the VM hardware version?
- VMTools up to date?
- Does the HAL match # of CPU’s?