cluster fails, the virtual machines fail to restart on a remaining host, or will only restart after a long delay.
The virtual machines were not protected by vSphere HA at the time the failure occurred.
Distributed Resource Scheduler was not enabled at the time the failure occurred.
There is insufficient spare capacity on hosts with which the virtual machines are compatible.
The virtual machines contain physical Raw Device Mappings.
Disable the network interface cards (NICs) to ensure that third-party drivers do not interfere with installation.
A networking problem between the source and destination hosts exists at the physical layer.
The virtual machine is not on shared storage visible to the source and destination hosts.
The vMotion migration priority for this migration was set to High.
The vMotion network is saturated.
An administrator is deploying vSphere 5.5.The administrator creates a vSphere Distributed Switch, then uses Auto Deploy to deploy several ESXi hosts. After the hosts are deployed, the administrator notices that LACP packets are NOT being sent between them.
LACP is NOT enabled on vCenter.
An administrator needs to establish that a database server is entitled to twice the CPU resources compared to a web server during CPU resource contention.
Which settings should the administrator change to accomplish this?
Set the database server#39;s CPU Shares to High and leave the web server#39;s CPU Shares at Normal.
Set the database server#39;s CPU Shares to High and change the web server#39;s CPU Shares to Low.
Set the database server#39;s CPU Shares to High and change the web server#39;s CPU Shares value to a Custom value of 500.
Set the database server#39;s CPU Shares to a Custom value of 500 and leave the web server#39;s CPU Shares at Normal.
The ESXi hosts must have root access to the datastore.
The NAS must support NFS version 4.
Port binding must be configured on the VMkernel port.
The MTU on the VMkernel port must be set to 9000.