Which of the following are requirements for successful VMotion migration (Choose Two)?
Virtual Machines must have access to the same subnets on the source and destination hosts
Gigabit Ethernet networking must exist between the source and destination hosts
Virtual Machines cannot be configured to use RDMs
CPUs with the same clock speed and cache size must exist on both the source and destination hosts
To enable the use of DRS migration recommendations, the hosts in your cluster must be part of a VMotion
network. If the hosts are not in the VMotion network, DRS can still make initial placement recommendations.
To be configured for VMotion, each host in the cluster must meet the following requirements:
The virtual machine configuration file for ESX/ESXi hosts must reside on a VMware Virtual Machine File System (VMFS).
VMotion does not support raw disks or migration of applications clustered using Microsoft Cluster Service (MSCS).
VMotion requires a private Gigabit Ethernet migration network between all of the VMotion enabled managed hosts. [B above].
Whilst it may not be an absolute requirement that virtual machines must have access to the same subnets on the source and destination hosts for VMotion to occur, if virtual machines do not have this access, then they can no longer communicate, thus rendering a VMotion migration un successful. [A is correct].
VMotion compatibility means that the processors of the destination host must be able to resume execution using the equivalent instructions where the processors of the source host were suspended. Processor clock speeds and cache sizes might vary, but processors must come from the same vendor class (Intel versus AMD) and same processor family to be compatible for migration with VMotion. [D is incorrect].
VMotion and RDMs
You can VMotion a VM that uses RDM as long as the RDM is configured in virtual compatibility mode. [C is incorrect].