Vmotions taking a long time?


I'm trying to troubleshoot some performance issues that we've been having and one thing I've noticed is that it appears that vmotioning from one host to another has been taking a few minutes.  I know there are more granular methods of finding this out, but is the attached event a fair representation of a that particular vmotion taking ~2.5 minutes, or am I misreading it?

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Normal observation, is there a problem with that....... is service affected ?

What's the problem DRS is moving the machine, DRS will wait until the right moment, e.g. Host and Guest low CPU to complete the move.

I would be more concerned if it failed!

vMotion is either a 1 or a 0, pass or fail!

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
blinkme323Author Commented:
Ok, so the initial time listed is when the vmotion was requested and the DRS time is the moment that it decided to actually vmotion the machine?
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
When the process was finished and over.

Also many events can delay it, number of vMotions active, cpu usage in VM and Host, also speed of VMKernel Interfaces, and how many...

It's not INSTANT!
blinkme323Author Commented:
Not trying to imply that it is instant.  What I'm trying to understand is if this this is a "normal" delay or something that could potentially impact that the underlying OS.  From what I understand, the vmotion won't occur unless the "stun time" is less than 500ms.  So if what I posted has no bearing on that, then I assume that the vmotions are fine.
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.