Can I employ LUN masking or zoning and still use VMotion?
A hard requirement for VMotion is that both the source and target ESX Servers have access to the VMFS volume that contains the virtual machine’s disk. If you have employed LUN masking or zoning to make the VMFS volume invisible to the target ESX Server, then you will not be able to use VMotion for any virtual machines stored on that invisible volume. Virtual Machines have no access to any other files on a VMFS volume, so a compromised guest operating system will not be able to compromise any of the other guest operating systems on the VMFS volume.