Книга: Mastering VMware® Infrastructure3
The Bottom Line
The Bottom Line
Manage virtual machine memory. The VMkernel is active and aggressive in its management of memory utilization across the virtual machines.
Master It A virtual machine needs to be guaranteed 1GB of RAM.
Master It A virtual machine should never exceed 2GB of physical memory.
Manage virtual machine CPU allocation. The VMkernel works actively to monitor, schedule, and migrate data across CPUs.
Master It A virtual machine must be guaranteed 1000 MHz of CPU.
Create and manage resource pools. Resource pools portion CPU and memory from a host or cluster to establish resource limits for pools of virtual machines.
Master It A resource pool needs to be able to exceed its reservation to provide for additional resource guarantees to virtual machines within the pool.
Configure and execute VMotion. VMotion technology is a unique feature of VMware Infrastructure 3 (VI3) that allows a running virtual machine to be moved between hosts.
Master It Identify the virtual machine requirement for VMotion. Master It Identify the ESX Server host requirements for VMotion.
Master It Five ESX Server hosts need to be grouped together for the purpose of enabling the Distributed Resource Scheduler (DRS) feature of VI3.
Configure and manage Distributed Resource Scheduling (DRS). DRS builds off the success and efficiency of VMotion by offering an automated VMotion based on an algorithm that analyzes system workloads across all ESX Server nodes in a cluster.
Master It A DRS cluster should determine on which ESX Server host a virtual machine runs when the virtual machine is powered, but it should only recommend migrations for VMotion.
Master It A DRS cluster should determine on which ESX Server host a virtual machine runs when the virtual machine is powered on, and it should also manage where it runs for best performance. A VMotion should only occur if a recommendation is determined to be a four- or five-star recommendation.
Master It Two virtual machines running a web application and a back-end database should be kept together on an ESX Server host at all times. If one should be the target of a VMotion migration, the other should be as well.
Master It Two virtual machines with database applications should never run on the same ESX Server host.