Oh man :smileygrin: That's really sick.

So you have to create these RelocateSpec and RelocateSpecDiskLocator objects etc. and then use some part of the API instead of having a high-level function for this task, wow.

As far as I understand it, internally to ESXi an svMotion actually is a vMotion, which is why you have to set a destination for all disks, even though you want to move only one of them, again wow.

Well, this also explains why the event log of vCenter Server shows both vMotion and svMotion as "Migrating from a to b" with no info about the datastore being changed for any specific disk (it only shows the destination disk in case you chose to migrate the VMX I guess).