Are you inquiring is the completion time difference supposed to be so drastic? Yes, and let me explain why...
Cloning is simply a copy of a VM at a point in time. The time it takes to do the copy depends on the variables listed above by arunraju.
Storage vMotion on the other hand is *moving* the VMDK to another location while it's "live". The reason why this process takes longer is because of the underlying technology that goes on from the beginning to the end of the sVMotion process. A snapshot is created of the orig VMDK (virtual disk), while the orig is being transferred to the new location. If data is changed on the virtual disk being moved, it is written to the snapshot file. Once the orig virt disk is moved, the snapshot then 'commits' all data to the orig virt disk file. Depending on what data is being written to it, and again...the factors shared by arunraju, the process will take considerably longer.
A bit more 'high-level' info on sVMotion:
http://www.vmware.com/files/pdf/VMware-Storage-VMotion-DS-EN.pdf (pg. 2)
Regards,
~coolsport00
Regards,
~coolsport00
