RemoteFX is an umbrella term for several technologies designed to enhance the Remote Desktop/VMConnect experience for VMs.

The values that this measure reports and their corresponding numeric values are listed in the table below:

Note:

By default, this measure reports the Measure Values listed in the table above to indicate whether /not RemoteFX is installed on a host. In the graph of this measure however, the same is indicated using the numeric equivalents only.

Using the detailed diagnosis of this measure, you can identify the host group and cluster to which a host belongs, and determine the domain name and operating system of that host.

Modern processors use the concepts of physical memory and virtual memory; running processes use virtual addresses and when an instruction requests access to memory, the processor translates the virtual address to a physical address using a page table or translation lookaside buffer (TLB). When running a virtual system, it has allocated virtual memory of the host system that serves as a physical memory for the guest system, and the same process of address translation goes on also within the guest system. This increases the cost of memory access since the address translation needs to be performed twice - once inside the guest system (using software-emulated shadow page table), and once inside the host system (using hardware page table).

In order to make this translation more efficient, processor vendors implemented technologies commonly called SLAT. By treating each guest-physical address as a host-virtual address, a slight extension of the hardware used to walk a non-virtualized page table (now the guest page table) can walk the host page table. With multilevel page tables the host page table can be viewed conceptually as nested within the guest page table. A hardware page table walker can treat the additional translation layer almost like adding levels to the page table.

Using SLAT and multilevel page tables, the number of levels needed to be walked to find the translation doubles when the guest-physical address is the same size as the guest-virtual address and the same size pages are used. This increases the importance of caching values from intermediate levels of the host and guest page tables. It is also helpful to use large pages in the host page tables to reduce the number of levels (e.g., in x86-64, using 2 MB pages removes one level in the page table-. Since memory is typically allocated to virtual machines at coarse granularity, using large pages for guest-physical translation is an obvious optimization, reducing the depth of look-ups and the memory required for host page tables.

The values that this measure reports and their corresponding numeric values are listed in the table below:

Note:

By default, this measure reports the Measure Values listed in the table above to indicate whether /not CPU SLAT is enabled on a host. In the graph of this measure however, the same is indicated using the numeric equivalents only.

NUMA stands for non-uniform memory architecture. In simplistic terms, NUMA allows for greater levels of scalability than traditional hardware expansion options, such as SMP. NUMA accomplishes this goal by eliminating what is a single choke point in traditional computing architecture: the memory bus. By adding more memory buses, a system can be scaled to greater heights. Each node in a NUMA architecture is generally considered a block of memory and the processors and I/O devices that are on the same physical bus as the aforementioned memory. Individual nodes are then aggregated through the use of an interconnect bus.

The values that this measure reports and their corresponding numeric values are listed in the table below:

Note:

By default, this measure reports the Measure Values listed in the table above to indicate whether/not NUMA spanning is enabled on a host. In the graph of this measure however, the same is indicated using the numeric equivalents only.

If a Host is set in Maintenance mode in SCVMM, then such a host “Saves” all the VMs in it.

In case of a two-node cluster, if you set maintenance mode for one node of the cluster, then it pauses the cluster role and it gives you an option if you want to save the VMs or live migrate them to the other node.

If you set the Maintenance mode for all nodes in a cluster, then it will save all the VMs as there is no place to Live Migrate them.

The values that this measure reports and their corresponding numeric values are listed in the table below:

Note:

By default, this measure reports the Measure Values listed in the table above to indicate whether/not a host is in the maintenance mode. In the graph of this measure however, the same is indicated using the numeric equivalents only.

The values that this measure reports and their corresponding numeric values are listed in the table below:

Note:

By default, this measure reports the Measure Values listed in the table above to indicate whether/not a host is available for placement. In the graph of this measure however, the same is indicated using the numeric equivalents only.

The values that this measure reports and their corresponding numeric values are listed in the table below:

Note:

By default, this measure reports the Measure Values listed in the table above to indicate the current state of a host. In the graph of this measure however, the same is indicated using the numeric equivalents only.

Using the detailed diagnosis of this measure, you can identify the host group and cluster to which a host belongs, and determine the domain name and operating system of that host.

The values that this measure reports and their corresponding numeric values are listed in the table below:

Note:

By default, this measure reports the Measure Values listed in the table above to indicate the current communication state of a host. In the graph of this measure however, the same is indicated using the numeric equivalents only.

If the value of this measure is close to 100% for any host, it means that that host is rapidly running out of CPU resources. Such a host may not be able to accommodate any more VMs.

In such a situation, use the detailed diagnosis of this measure to know which VMs on the host are the leading consuming of its CPU resources. You may want to find out which resource-intensive processes are running on such VMs, as they could be the ones causing the CPU contention.

This is used for placement decisions for new VMs.

Use the detailed diagnosis of this measure to know how much memory has been assigned to each VM on the host, the demand for that memory, the percentage of memory free on that VM, and the disk space allocated to that VM.

A high value is desired for this measure. A consistent decrease in the value of this measure, is a sign that memory resources are being eroded.

If the value of this measure is close to 100% for any host, it means that that host is rapidly running out of memory resources. Owing to the memory constraint, such a host may not be able to accommodate any more VMs.

You can use the detailed diagnosis of this measure to know which VM on the host is starved for memory resources.

A high value is desired for this measure. If the value of this measure drops consistently for a host, then it means that that host's remote storage space is being eroded. If the situation persists, then soon, the host will be left with very little remote storage space to work with.

A low value is desired for this measure. If the value of this measure increases consistently for a host, then it means that that host is over-utilizing it's remote storage space.

If the value of this measure is 100% or close to it for any host, it is a clear indication that the host is running out of remote storage space. You can add to the remote storage capacity of those specific hosts to avert any potential remote storage space contention.

A high value is desired for this measure. If the value of this measure drops consistently for a host, then it means that that host's local storage space is being eroded. If the situation persists, then soon, the host will be left with very little local storage space to work with.

A low value is desired for this measure. If the value of this measure increases consistently for a host, then it means that that host is over-utilizing it's local storage space.

If the value of this measure is 100% or close to it for any host, it is a clear indication that the host is running out of local storage space. You can add to the storage local capacity of those specific hosts to avert any potential local storage space contention.

A high value is desired for this measure. If the value of this measure drops consistently for a host, then it means that that host is running out of storage space. If the situation persists, then soon, the host will be left with very little storage space to work with.

A low value is desired for this measure. If the value of this measure increases consistently for a host, then it means that that host is over-utilizing it's storage space.

If the value of this measure is 100% or close to it for any host, it is the sign of a potential storage space crunch on the host. You can add to the storage capacity of those specific hosts to avert any potential storage space contention.

This measure is used for placement decisions of new VMs.

You can use the detailed diagnosis of this measure to know how much disk I/O is utilized by each VM on the host. This will point you to the exact VM that is excessively utilizing the disk I/O resources.

This measure is used for placement decisions of new VMs.

This measure is used for placement decisions of new VMs.

You can use the detailed diagnosis of this measure to know how each VM on the host is utilizing the network resources. This way, you can quickly identify VMs that are hogging the network resources of the host.

The values that this measure reports and their corresponding numeric values are listed in the table below:

Note:

By default, this measure reports the Measure Values listed in the table above to indicate the whether/not the host supports the live migration feature. In the graph of this measure however, the same is indicated using the numeric equivalents only.listed in the table above to indicate the whether/not the host supports the live migration feature. In the graph of this measure however, the same is indicated using the numeric equivalents only.

The values that this measure reports and their corresponding numeric values are listed in the table below:

Note:

By default, this measure reports the Measure Values listed in the table above to indicate the whether/not live migration is enabled for the host. In the graph of this measure however, the same is indicated using the numeric equivalents only.

The values that this measure reports and their corresponding numeric values are listed in the table below:

Note:

By default, this measure reports the Measure Values listed in the table above to indicate the whether/not a subnet can be used for migration. In the graph of this measure however, the same is indicated using the numeric equivalents only.

Use the detailed diagnosis of this measure to know which VMs on the host are powered on.

Use the detailed diagnosis of this measure to know which VMs on the host are powered off.

Use the detailed diagnosis of this measure to know which VMs on the host are neither in a powered off, nor in a powered on state.

An “orphaned” virtual machine is one that exists in the vCenter Server database but is no longer present in ESX host inventory.

Virtual machines can become orphaned if a host failover is unsuccessful, or when the virtual machine is unregistered directly on the host. If this situation occurs, move the orphaned virtual machine to another host in the data center on which the virtual machine files are stored.

A VM template is a master copy image of a virtual machine that includes VM disks, virtual devices, and settings. A VM template can be used many times over for the purposes of VM cloning. You cannot power on and edit the template once it has been created.