Книга: Mastering VMware® Infrastructure3

Chapter 9: Managing and Monitoring Resource Access

Chapter 9: Managing and Monitoring Resource Access

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.

Solution Configure the virtual machine with a 1GB reservation.

Master It A virtual machine should never exceed 2GB of physical memory.

Solution Configure the virtual machine with a 2GB limit.

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 1000MHz of CPU. Solution Configure the virtual machine with 1000MHz 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.

Solution Configure the resource pool with an expandable reservation.

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.

Solution Virtual machines cannot be connected to a CD-ROM or floppy image on a nonshared datastore. Virtual machines cannot be connected to an internal-only virtual switch. Virtual machines cannot be part of a Microsoft Server Cluster. Virtual machines cannot be configured with CPU affinity.

Master It Identify the ESX Server host requirements for VMotion.

Solution Both ESX Server hosts must have access to the same storage devices (fibre channel, iSCSI, and NAS devices). Both ESX Server hosts must have exactly the same labeled virtual switches that provide access to the same physical networks configured with the same IP subnets. Both ESX Server hosts must have compatible CPUs (CPU family, CPU vendor, SSE instructions, VT configuration, NX/XD configuration). Both ESX Server hosts must have access to the same VMotion network.

Create and manage clusters.

Master It Five ESX Server hosts need to be grouped together for the purpose of enabling the Distributed Resource Scheduler (DRS) feature of VI3.

Solution Create a cluster object in the VirtualCenter inventory and enable DRS on the cluster.

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.

Solution Configure the DRS cluster to use the Partially Automated setting.

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.

Solution Configure the DRS cluster to use the Fully Automated setting with the moderately conservative setting.

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.

Solution Configure both virtual machines in an affinity rule that keeps the virtual machines together.

Master It Two virtual machines with database applications should never run on the same ESX Server host.

Solution Configure the virtual machines in an anti-affinity rule that separates the virtual machines.

Оглавление книги