1 person found this helpful
vMotion is supported migrating both compute and storage simultaneously. Shared storage is not mandatory. See here: Migration with vMotion in Environments Without Shared Storage
Other than that vMotion between 2 sites is not the only use case of extending L2 between sites and using Cross-VC NSX. You might also have replication being done between storage on either site so you can recover and bring up VMs on another site without changing IP address.
I imágened that vMotion always needs a shared storage so the service behind the scenes movies only VM configs from utilizing a host to another one, Now I think the behind the scenes service that provides us the vMotions has privileges to access, creates a shadow copy from the running VM compresses it, moves into another host another storage and then decompresses it running into the new chosen host