How actually Vmotion and SVmotion works with different % of completion or failure at different %

vMotion - just moves the VM process between hosts, no data is moved, it remains on the datastore.

Storage vMotion - moves the virtual disks, (vmdks) between datastores.

Both use the vMotion network, but are very different process.

Thanks Andrew, would need you expert advise to understand the % criteria for Vmotion and Svmotion ?

like most of the time it takes long time @ 18%,26 %,32 % and 95% or stuck @specific % in process .

Hope now i have clarified  my question to you.

95% means sommiting all data to disk. It will go ahead when data is safe on destination disk/host

grate ,thanks.

what about @32 %..if it got stuck ..is there any permanent solution to get this resolved ?

@Andrew..I have alreday shared vmkernel logs snap in my another question.. so would appreciate your expert advise on same.

And here i need to understand if this time out  error is coming due to topology(way how svmotion works/process in 4.1 and 5.1 ) changed in 5.1, as earlier it was something different.. how svmotion or vmotion works.

 That is why i need to understand this % wise calculation for Svmotion in 5.1..or if it is still same as it was in 4.1 ?

Case already  logged with VM Support for issue..but would really appriciate  if here we can get the expert advise for same to get this more explored .

Please post logs here.

Thanks Andrew for all your supportive commnets here..but further i will riase this concern to VMware

Thanks