Our application successfully invokes function VixDiskLib_PrepareForAccess() the operation result is VIX_OK.
The resulting effect is different based on the state of the virtual machine.
For powered-on virtual machine the context menu option "Migrate..." is still available and migration to another host can be started.
For powered-off virtual machine the option "Migrate ..." is blocked and migration can not be started.
Could someone please explain the behavior of the API?
How to disable vMotion for the powered-on virtual machine?
I would appreciate to any information related to this topic.
We use VDDK 6.0, vCenter Server 6.0