Hello, a costumer started to claim that it could not start some VMs, I took a look and saw that the VM was in vMotion process, but it took 14 minutes to finish.
I took some time to analysis the log, for now I didn't discovery the issue yet.
What is the network between the source and destination hosts?
How much memory is the VM allocated?
Was the VM workload very active during the migration?
Hello Scott, thanks for your reply.
New interesting thing, this is happening when powering on machines too...
Now is 09:25 PM this machine started to power on at 8:39 PM
UPDATE:
OK Let me answer, I don't have the workload from the other time, now it´s (the load doesn´t change much through the day because its a hospital):
All machines have 3 to 6 GB RAM
The network for this servers are 10GbE through Cisco 6120 for blade systems, all hosts are in enclosure.