VS5ICM M10 ResourceMonitoring PDF
VS5ICM M10 ResourceMonitoring PDF
Module 10
virtual machine
There are 3 layers of memory
in VMware vSphere®.
Guest OS virtual memory is application
guest OS
presented to applications virtual memory
by the operating system.
Guest OS physical memory operating guest OS
is presented to the virtual physical memory
system
machine by the VMkernel.
Host physical memory
managed by the VMkernel VMware®
provides a contiguous, ESXi host
ESXi™ host
addressable memory space physical memory
that will be used by the
virtual machine.
overhead memory
Swap file size equals the difference
between allocated and reserved
memory
VM 1 VM 2 VM 3
256 MB 256 MB 256 MB
.vswp .vswp .vswp
Decompressing a
compressed page in memory
is faster than performing disk
I/O operations.
Compression only takes
place when there is
contention for physical
memory resources. = memory compression cache
reservation
0 MHz/MB
VM A VM B VM C
Configured by
Adjustable by
Managed by VMkernel virtual machine
administrator
creator
• Hyperthreading • VMware • Limit
CPU vSphere Virtual
• Load balancing • Reservation
cycles Symmetric
• NUMA Multiprocessing • Share allocation
• Transparent page
sharing
• Limit
• vmmemctl • Available
• Reservation
RAM • Memory compression memory
• Share allocation
• VMkernel swap files
for virtual machines
Disk
• Virtual machine
bandwidth • Multipathing
file location
A resource pool is a
logical abstraction for
hierarchically managing
CPU and memory
resources.
It is used on standalone
hosts or clusters enabled
root
for vSphere Distributed resource
Resource Scheduler resource
pool
(DRS). pools
No
No Expandable
Fail
reservation?
In this lab, you will create and use resource pools on an ESXi host.
1. Create CPU contention.
2. Create a resource pool named Fin-Test.
3. Create a resource pool named Fin-Prod.
4. Verify resource pool functionality.
Assess performance.
Use appropriate monitoring
tools.
Record a numerical
benchmark before changes.
Identify the limiting resource. Do not make casual changes
to production systems.
Make more resources
available.
Allocate more.
Reduce competition.
Log your changes.
Benchmark again.
Iometer
Task Manager
Task Manager in
guest operating system
CPU Usage
chart for host
In this lab, you will see how CPU workload is reflected by system
monitoring tools.
1. Use vCenter Server to monitor CPU utilization.
2. Undo changes made to your virtual machines.
Avoid
small
fluctuations.
Avoid
repeats.
Select SNMP to
specify trap
destinations.
In this lab, you will demonstrate the vCenter Server alarm feature.
1. Create a virtual machine alarm that monitors for a condition.
2. Create a virtual machine alarm that monitors for an event.
3. Trigger virtual machine alarms and acknowledge them.
4. Disable virtual machine alarms.