sapnote_0001482272

11.05.2012 Page 1 of 6

SAP Note 1482272 - Key Figures of Virtualization on VMwarevSphere

Note Language: English Version: 7 Validity: Valid Since 08.05.2012

Summary

SymptomYou need to get background information about the Windows operating systemthe SAP system is running on.You require configuration information and performance data related to theSAP system installed on Windows and running in a virtual environment onVMware vSphere.

Most of the information of this SAP note is also valid for an SAP systemrunning on Linux in a virtual environment on VMware vShere.

Other termsST06, OS07, OS07N, SAPOSCOL, DUMP CCM, virtualization, VMware, enhancedmonitoring

Reason and PrerequisitesIf the Enhanced Monitoring for virtualization is activated as described inSAP Note 1409604, the operating system-specific information is enriched byvirtualization-specific information. You can access this information eitherin the SAP system, or at the command prompt on operating system levelwithin a virtual machine.

This note describes the actual virtualization-specific data set, which canbe split into platform-independent data and into virtualizationsolution-specific data.

Besides this data set, SAP note 1260719 describes an earlier CIM based dataset of virtualization-specific data on Windows that is additionallyavailable. For SAP systems that are running with an older support packageversion, only this data set might be available within the SAP system.

SolutionIn the SAP system, virtualization-specific data is available viatransaction ST06 (as of SAP NetWeaver Release 7.2), OS07 (for SAP NetWeaverRelease 7.1) or OS07N (for SAP NetWeaver Release 6.40 and 7.0x). Forrelease details, see SAP note 1483047. These transactions offer the'Standard view' or the 'Expert view', which you can display with therelevant menu button. The 'Standard view' provides the most important andmainly platform-independant key figures of virtualization. The 'Expertview' provides detailed platform-specific data of the virtualization layer.

At the command prompt on operating system level within the virtual machine,you get the data by using the command "SAPOSCOL.EXE -d".In the dialog mode of SAPOSCOL, the command "dump ccm" displays thevirtualization-specific data set.

The following sections provide an overview of the categories and theirmetrics that are available for SAP applications running on VMware vSphere.For SAP applications running on VMware ESX version 3.x, some of the listedmetrics are not available.

For more information about Performance Monitoring on VMware, see also

11.05.2012 Page 2 of 6


http://www.sdn.sap.com/irj/sdn/windows-virtualization?rid=/webcontent/uuid/30d43087-6057-2c10-c1b8-e0ba068b1ceb#section6

Virtualization ConfigurationThe following fields are available in this metrics category:

o SolutionConstant for the virtualization solution that hosts the virtualmachine. On VMware, this value is VIRT_METHOD_VMWARE_ESX.

o ManufacturerManufacturer of the virtualization solution that hosts the virtualmachine.Refers to the field 'System Manufacturer' from the Windowssysteminfo; for a virtual machine running on VMware this value is"VMware, Inc.".In a native environment, this field contains the manufacturer ofthe computer.

o Model or TypeProduct information of the virtualization solution installed.Both fields refer to the field 'System Model' from the Windowssysteminfo; for a virtual machine running on VMware this value is"VMware Virtual Platform".In a native environment, this field contains the product name thatthe manufacturer gave to the computer.

o Solution VersionVersion information of the virtualization solution installed.On VMware, this is the version of the VMware tools installed insidethe virtual machine.

o Enhanced Monitoring StatusIf the VMware guest SDK is not correctly installed, theconfiguration of enhanced monitoring has to be checked. In thiscase, the 'Enhanced Monitoring Status' contains a warning.

CPU Virtualization Virtual SystemDuring the configuration of the virtual system, you can select the numberof virtual CPUs. Each virtual CPU corresponds to the amount of CPU cyclesof a logical CPU on the host.The number of logical CPUs on the host is the number of physical processorcores or two times this number when hyperthreading is enabled.

The following fields are available in this metrics category:

o Capacity ConsumedNumber of CPUs used inside the virtual system at this time.Unit: CPUs (logical processors)

o Additional Capacity AvailableAdditional capacity available from host and pool for use insidethis virtual system (not consumed now).This value corresponds to the number of physical CPUs that areavailable besides the CPUs that are currently used inside thisvirtual system; min ('free on host and pool' | 'Capacity Limit VS')Unit: CPUs

11.05.2012 Page 3 of 6


o Available CapacitySum of 'Capacity Consumed' and 'Additional Capacity Available'.Unit: CPUs

o Available Capacity ConsumedPercentage of 'Available Capacity' that has been consumed.Unit: PercentRange: 0..100

o Guaranteed Capacity (Reservation)Capacity reserved for this virtual machine even if other VMs createprocessor load on the host.By default, no reservation is set, and the value is set to zero.This value corresponds to the field 'Reservation' in the 'ResourceAllocation Tab' of the virtual system.Unit: CPUs (logical processors)

o Guaranteed Capacity ConsumedPercentage of 'Guaranteed Capacity' that has been consumed by thisvirtual system. This counter can exceed 100%.Unit: PercentRange: 0..>100

o Capacity LimitMaximum amount of physical host CPUs available to the virtualmachine.By assigning a limit, this virtual system can never consume morethan the configured amount of available host CPUs.By default, no limit is set, and the value is set to zero.This value corresponds to the field 'Limit' in the 'ResourceAllocation Tab' of the virtual system.A virtual system can allocate more CPU than guaranteed but itcannot assign more than its limit.Unit: CPUs (logical processors)

o CPU Shares AllocatedCPU Shares allocated to the virtual machine.This number determines which virtual system gets resources whenthere is competition for resources among virtual systems.This value corresponds to the field 'Shares' in the 'ResourceAllocation Tab' of the virtual system.The amount of resources represented by each share changes when anew virtual machine is powered on. This affects all virtualmachines.

Example:Two virtual machines run on a host with 8 GHz. Both are set tonormal priority and get 4 GHz each. A third virtual machine ispowered on. It is set to High priority, which means it should havetwice as many shares as the machines set to normal. The new virtualmachine receives 4 GHz and the two other machines only get 2 GHzeach.Unit: None

o StealTimeNumber of milliseconds that the virtual machine was in a readystate (able to transition to a run state), but was not scheduled to

11.05.2012 Page 4 of 6


run.Unit: ms

CPU Virtualization HostThe fields of this metrics category are displayed in Expert View mode only.

o Maximum Processor FrequencyMaximum processor frequency of the underlying hardware.

o Physical CPUsAmount of physical CPU cores on the host.This figure does not show whether Hyperthreading is activated ornot.Unit: CPU (cores)

o Physical CPUs ConsumedPercentage of physical CPUs used at this time.Unit: Percent

Memory Virtualization Virtual SystemThe following fields are available in this metrics category:

o Memory ConfiguredAmount of memory that is available for the guest OS and theapplications that are running inside the virtual system.A virtual machine cannot benefit from more memory than itsconfigured memory size; this memory must no be backed by physicalmemory on the host.This value corresponds to the field 'Memory' in the 'Hardware Tab'of the virtual system.Unit: MB

o Guaranteed MemoryHost physical memory reserved for this virtual machine even if hostmemory is overcommitted.Unit: MB

o Memory LimitUpper limit of host physical memory comsumed for the virtualmachine.By default, no limit is set. This means that the maximum allocatedhost physical memory of a virtual machine is the same as itsconfigured memory size.Unit: MB

o Memory BalloonedAmount of memory that has been reclaimed from this virtual machineby ballooning.Ballooning reflects guest memory pressure. By inflating theballoon, a virtual machine consumes less physical memory on thehost, and more physical memory on the guest.If the value reported for 'Memory Ballooned' is higher than zero,this indicates a first phase of memory pressure. In this case, theMemory Bottleneck Indicator changes from status green to statusyellow.Unit: MB

o Memory Swapped Out

11.05.2012 Page 5 of 6


Amount of memory that has been reclaimed by this virtual system byswapping.If ballooning is not sufficient to reclaim memory, or the host freememory drops towards the hard treshold, the hypervisor starts touse swapping in addition to using ballooning.At virtual machine startup, the hypervisor creates a separate swapfile for the virtual machine. If necessary, the hypervisor can thendirectly swap out guest physical memory to the swap file, whichfrees host physical memory for other machines.Swapping in pages is expensive for the VM and can decreaseperformance.If the value reported for 'Memory Swapped Out' is higher than zero,this indicates a second phase of memory pressure. In this case, theMemory Bottleneck Indicator changes from status yellow to statusred.Unit: MB

o Memory Bottleneck IndicatorIndicator for Memory Health of the virtual machine (range 0.. 10).If the virtual machine has sufficient memory resources, the MemoryBottleneck Indicator is set to 0 (status green).If memory is ballooned, the Memory Bottleneck Indicator is set to 6(status yellow).If memory is swapped out, the Memory Bottleneck Indicator is set to8 (status red).

o Memory Overhead (Expert view only)Amount of extra host memory needed by the hypervisor for managementbesides the memory allocated to the virtual machine.Its size depends on the number of virtual CPUs and the configuredvirtual machine memory size.Unit: MB

o Memory Shares Allocated (Expert view only)Amount of memory shares allocated to the virtual machine.The more shares the virtual machine has, the more often it gets atime slice of a memory when there is no memory idle time.When the hypervisor needs memory, it reclaims memory from thevirtual machine that owns the fewest shares-per-allocated page.Unit: None

Memory Virtualization HostThe fields of this metrics category are displayed in Expert View mode only.

o Physical MemoryTotal amount of physical memory owned by the host operating systemkernel.Unit: MB

o Physical Memory ConsumedTotal amount of consumed memory on the host.This includes memory used by the host to support the physicaladdress space of all the virtual machines on the host.Unit: Percent

o Memory Swapped OutTotal amount of memory that is swapped out for all virtual machineson the host.

11.05.2012 Page 6 of 6


Unit: MB

o Memory SharedMemory pages that are shared within a single guest and memory thatis shared between guests.Unit: MB

o Memory OverheadTotal amount of kernel memory overhead on the host.Unit: MB

Header Data

Release Status: Released for CustomerReleased on: 08.05.2012 09:26:07Master Language: EnglishPriority: Recommendations/additional infoCategory: ConsultingPrimary Component: BC-OP-NT Windows

Secondary Components:BC-OP-LNX Linux

BC-OP-NT-ESX Windows on VMware ESX

Valid Releases

Software Component Release FromRelease

ToRelease

andSubsequent

KRNL32NUC 7.21 7.21 7.21

KRNL32NUC 7.21EXT 7.21EXT 7.21EXT

KRNL32UC 7.21 7.21 7.21

KRNL32UC 7.21EXT 7.21EXT 7.21EXT

KRNL64NUC 7.21 7.21 7.21

KRNL64NUC 7.21EXT 7.21EXT 7.21EXT

KRNL64UC 7.21 7.21 7.21

KRNL64UC 7.21EXT 7.21EXT 7.21EXT

SAP_BASIS 60 640 640



KERNEL 72 7.21 7.21

Related Notes

Number Short Text

1606643 Linux: VMware vSphere host monitoring interface

1483047 "Old" version of operating system monitor not available

1260719 SAPOSCOL: Detailed virtualization data

1102124 SAPOSCOL on Linux: Enhanced function

171356 SAP software on Linux: Essential information

Documents

sapnote_0001482272