VSICM7 M08 Resource Manage Monitor
VSICM7 M08 Resource Manage Monitor
and Monitoring
© 2020 VMware, Inc. VMware vSphere: Install, Configure, Manage [V7] | 8-2
Module Lessons
1. Virtual CPU and Memory Concepts
2. Resource Controls
3. Resource Monitoring Tools
4. Monitoring Resource Use
5. Using Alarms
© 2020 VMware, Inc. VMware vSphere: Install, Configure, Manage [V7] | 8-3
Virtual Beans: Resource Management and Monitoring
Virtual Beans wants to proactively manage and monitor its vSphere environment.
Virtual Beans administrators must be able to:
• Increase allocation of CPU and memory resources for business-critical workloads, particularly
during peak months.
• Monitor VM performance to troubleshoot user problems.
• Monitor ESXi host performance to avoid potential problems in the infrastructure.
• Create monthly reports, for management, that contain graphs of VM resource usage.
• Set notifications for when ESXi hosts experience high resource use.
As a Virtual Beans administrator, you must use the available tools in vSphere for managing and
monitoring the vSphere environment.
© 2020 VMware, Inc. VMware vSphere: Install, Configure, Manage [V7] | 8-4
Lesson 1: Virtual CPU and Memory Concepts
© 2020 VMware, Inc. VMware vSphere: Install, Configure, Manage [V7] | 8-6
Memory Virtualization Basics
vSphere has the following layers of memory:
• Guest OS virtual memory is presented to
applications by the operating system.
• Guest OS physical memory is presented to
the virtual machine by the VMkernel.
• Host machine memory that is managed by
the VMkernel provides a contiguous,
addressable memory space that is used by
the VM.
© 2020 VMware, Inc. VMware vSphere: Install, Configure, Manage [V7] | 8-7
VM Memory Overcommitment
Memory is overcommitted when the combined
configured memory footprint of all powered-on
VMs exceeds that of the host memory sizes.
When memory is overcommitted:
• VMs do not always use their full allocated
memory.
• To improve memory usage, an ESXi host
transfers memory from idle VMs to VMs that
need more memory.
• Overcommitted memory is stored in the
.vswp file.
• Memory overhead is stored in the vmx-
*.vswp file.
© 2020 VMware, Inc. VMware vSphere: Install, Configure, Manage [V7] | 8-8
Memory Overcommit Techniques
An ESXi host uses memory overcommit techniques to allow the overcommitment of memory
while possibly avoiding the need to page memory out to disk.
Methods Used by the ESXi Host Details
Transparent page sharing This method economizes the use of physical memory pages. In this
method, pages with identical contents are stored only once.
Ballooning This method uses the VMware Tools balloon driver to deallocate
memory from one VM to another. The ballooning mechanism
becomes active when memory is scarce, forcing VMs to use their
own paging areas.
Memory compression This method tries to reclaim some memory performance when
memory contention is high.
Host-level SSD swapping Use of a solid-state drive on the ESXi host for a host cache swap
file might increase performance.
VM memory paging to disk Using VMkernel swap space is the last resort because of poor
performance.
© 2020 VMware, Inc. VMware vSphere: Install, Configure, Manage [V7] | 8-9
Configuring Multicore VMs
You can build VMs with multiple virtual CPUs (vCPUs). The number of vCPUs that you configure
for a single VM depends on the physical architecture of the ESXi host.
A trigger can monitor the current condition or A trigger can monitor events that occur in
state of an object, for example: response to operations occurring on a managed
• A VM’s current snapshot is more than 2 GB. object, for example:
• A host is using 90 percent of its total memory. • The health of a host’s hardware changes.
• A datastore is disconnected from all hosts. • A license expires in the data center.
• A host leaves the distributed switch.