IBM Endpoint Manager, Version 9.0

Kernel-based Virtual Machine

Kernel-based Virtual Machine is one of the virtualization technologies supported by Subcapacity Reporting.

Purpose

Kernel-based Virtual Machine (KVM) represents the latest generation of an open source virtualization. KVM is a full virtualization solution for Linux on x86 hardware containing virtualization extensions (Intel VT or AMD-V). In the KVM architecture, each guest (virtual machine) is implemented as a regular Linux process. After you install KVM, you can run multiple guests, with each of them running a different operating system image. Each of these virtual machines has private, virtualized hardware, which includes memory, storage, graphics adapter, and a network card. This allows KVM to benefit from all the features of the Linux kernel.

Red Hat Entreprise Virtualization Manager (RHEV-M)

Red Hat Enterprise Virtualization (RHEV) is an enterprise virtualization product based on the KVM hypervisor. RHEV-M is a service running on a Red Hat Enterprise Linux server that provides interfaces for controlling the virtualization platform. It manages provisioning, connection protocols, user sessions logins and logoffs, virtual desktop pools, virtual machine images, and the high availability and clustering systems. RHEV-M provides the REST API that is used by Subcapacity Reporting to collect information about the whole infrastructure that is managed by RHEV-M.

The default URL that is to be used:

For RHEV-M 3.0
```
https://<RHEV-M_IP_address>:8443/api
```
For RHEV-M 3.1
```
https://<RHEV-M_IP_address>:443/api
```

Important: Different definitions of users are used for Microsoft Hyper-V, VMware, and RHEV-M:

For Microsoft Hyper-V, the user is defined as user_name\domain, for example: test\cluster.com
For VMware, the user is defined as domain\user_name, for example: cluster.com\test
For RHEV-M, the user is defined as user_name@domain, for example: test@cluster.com

Supported versions:

Red Hat Enterprise Virtualization Manager 3.0 and 3.1

Diagram showing the communication between the server and RHEV-M

Important: Different definitions of users are used for Microsoft Hyper-V and VMware:

For Microsoft Hyper-V, the user is defined as user_name\domain, for example: test\cluster.com
For VMware, the user is defined as domain\user_name, for example: cluster.com\test

Feedback