vSphere Virtual Machines view

A vSphere virtual machine (VM) is an isolated software container that can run its own applications and operating systems as if it were a stand-alone physical computer. It behaves exactly like a physical computer and has its own virtual (software-based) CPU, memory, storage and network interfaces, and allow flexible and dynamic allocation of CPU and memory resources.

Settings for vSphere Virtual Machines view

You can use the Settings page to configure the settings for all pages in the vSphere Virtual Machines view. To access this page, on the vSphere Virtual Machines view page, select Settings icons.png > Edit Settings.

Local settings

You can manage the local thresholds by configuring the Other Settings.

Field

Description

Other Settings

Top/Bottoms VMs Rank - CPU Weight

Edit the required vSphere Virtual Machines CPU Weight. This factor is used to Rank VMs in the view.

Top/Bottoms Partition Rank - Memory Weight

Edit the required vSphere Virtual Machines Memory Weight. This factor is used to Rank VMs in the view.

Top/Bottoms Partition Rank - Storage Weight

Edit the required vSphere Virtual Machines Storage Weight. This factor is used to Rank VMs in the view.

Show VM Templates

Click to enable or disable the display of VM templates in the vSphere Virtual Machines view.

CPU Starved VMs - CPU Ready [%] Threshold

Edit the required CPU Ready [%] Threshold for the CPU Starved VMs.

High File System Usage VMs - FS Usage Threshold

Edit the required FS Usage Threshold for the High File System Usage VMs.

Memory starved VMs - Ballooning [MB] Threshold

Edit the required Ballooning [MB] Threshold for the Memory starved VMs.

Memory starved VMs - Swap Rate [KB/s] Threshold

Edit the required Swap Rate [KB/s] Threshold for the Memory starved VMs.

Memory starved VMs - Memory Usage [%] Threshold

Edit the required Memory Usage [%] Threshold for the Memory starved VMs.

High Latency VMs - Times Latency Exceed Threshold

Edit the required Times Latency Exceed Threshold for the High Latency VMs.

High Latency VMs - Latency (msec) Exceed Threshold

Edit the required Latency (msec) Exceed Threshold for the High Latency VMs.

Optimization behavior

Optimization behavior	Description
Aggressive	Resource utilization in the server is computed by considering the average value of hourly samples. Spikes in the resource utilization within the hour are not considered. Then, 95^th percentile of the hourly value over the last 30 days is computed for each resource to generate the configuration of the target virtual machine or instance type.
Balanced (Default)	Resource utilization in the server is computed by considering the 90^th percentile value of hourly samples. Only 10% of spikes in the utilization within the hour are not considered. Then, 95^th percentile of the hourly value over the last 30 days is computed for each resource to generate the configuration of the target virtual machine or instance type.
Conservative	Resource utilization in the server is computed by considering the 99^th percentile value of hourly samples. Only 1% of spikes in the utilization within the hour are not considered. Then, 95^th percentile of the hourly value over the last 30 days is computed for each resource to generate the configuration of the target virtual machine or instance type.

Information

If you select the Conservative or Balanced optimization behavior for a server that is not instrumented, the results are based on the Aggressive behavior.

BMC recommends the Conservative behavior for servers that are running business-critical applications.

Data views

Displays the details when the view was last refreshed. Click Refresh views to refresh all vSphere Virtual Machines views. After you click this button, all vSphere Virtual Machines views are scheduled for materialization.

The option to Refresh views is available only if your user role has permissions to edit the view. For more details about permissions, see Adding-and-managing-roles.