Red Hat Virtualization Manager is a free application that will help you install and configure the Red Hat Enterprise Linux Virtualization (RHEV) Manager, RHEL VMWare Tools, and other products.
RedHat Virtualization Manager (RHVM) is an application that allows you to run multiple Linux instances from a single server. RHVM also enables you to create and manage virtual machines from the command line. RHVM is a component of Red Hat Enterprise Linux (RHEL). RHVM is available in the standard Red Hat Enterprise Linux distributions. RHVM is also available as an RPM package. RHVM comes with a command line interface, which allows you to manage virtual machines from the command line. RHVM can be installed on Linux server systems from RHEL, CentOS, or Scientific Linux. RHVM is available in the standard Red Hat Enterprise Linux distributions. RHVM is also available as an RPM package. RHVM comes with a command line interface,
RedHat Virtualization Manager
Red Hat Virtualization Manager (RHVM) provides a centralized platform for managing the physical and logical resources of a Red Hat virtualization environment. Red Hat Virtualization Manager is built on Red Hat Enterprise Linux and Red Hat JBoss Enterprise Application Platform. It uses a PostgreSQL database to store information and offers several management interfaces, including a REST API.
Before you install Red Hat Virtualization Manager (RHVM), the server hardware and operating system must meet the following requirements These requirements apply to Red Hat Virtualization 4.1.
The following table shows the minimum and recommended hardware requirements for Red Hat Virtualization Manager 4.1 :
|Processor||A dual-core processor||A quad-core processor or multiple dual-core processors|
|Memory||4 GB available system RAM (not occupied by existing processes)||16 GB available system RAM (not occupied by existing processes)|
|Memory||25 GB locally available and writable hard disk space||50 GB locally available and writable hard disk space|
|Network||1 network interface card (NIC) with a bandwidth of at least 1 Gbit/s||1 network interface card (NIC) with a bandwidth of at least 1 Gbit/s|
Message: The equipment requirements in this table are based on a typical small to medium sized installation. The exact requirements depend on the size, amount of work and period for which the records are kept. These recommendations are provided as guidance.
Red Hat Virtualization Manager and all hosts must have fully resolved domain names and forward and reverse DNS records. All DNS services used by the Red Hat Virtualization environment must be hosted outside the environment.
Red Hat Virtualization Manager requires multiple network ports for external and internal services to function properly. The engine-setup command used to configure the RHVM server can also automatically configure the firewall. However, it overwrites any existing user-iptables rules unless you use firewalld to manage them. The engine-setup command populates the list of required iptables rules in /etc/ovirt-engine/iptables.example.
Installation and configuration process
The installation and configuration process of Red Hat Virtualization Manager can be divided into three steps:
1. Install the base version of Red Hat Enterprise Linux 7 on the server, subscribe to Red Hat Enterprise Linux and Red Hat Virtualization, and activate the appropriate channels or software repositories.
2. Install the Red Hat Virtualization Manager software package on the server.
3. Configure Red Hat Virtualization Manager using the engine-setup command.
Step 1: Install the operating system and activate software repositories
Install Red Hat Enterprise Linux 7 Server only with the Base package group on the system where Red Hat Virtualization Manager will be deployed. This ensures that only the required packages are installed on the system and that there are no conflicts between packages from different program channels when installing Red Hat Virtualization Manager.
The system must be registered and logged on with Red Hat Enterprise Linux and Red Hat Virtualization Software privileges to install packages and updates from the Red Hat Content Distribution Network or Red Hat Satellite server.
Register the system in a Customer Portal account that has rights assigned for Red Hat Enterprise Linux Server and Red Hat Virtualization :
[email protected] ~]# subscription-manager register
Next, set up the pool IDs for the subscriptions that offer Red Hat Enterprise Linux Server and Red Hat Virtualization. Use these pool IDs to link subscriptions to your server. Use the subscription-manager list command to display the available subscriptions for the customer portal account you registered your server with. If you do, you might see something like the following:[[email protected] ~]# subscription-manager list –available|less
Subscription Name : Red Hat Virtualization (2 sockets), Standard
Provides : JBoss Enterprise Application Platform
Red Hat JBoss Core Services
Red Hat Virtualization Host
Red Hat Virtualization
Contract: …not applicable…
Pool ID : 1234567890123456789012
Provides control : Not available
Level of service : Standard
Type of service : L1-L3
Type of subscription : Stackable ends
System type: Physics
Then use the pool ID to join a pool that gives your server the necessary rights:[[email protected] ~]# subscription-manager attach –pool=1234567890123456789012
Subscription successfully attached for : Red Hat Virtualization (2 sockets), default
[[email protected] ~]#
Message: You may need to join multiple pools to get both permissions for your server. For example, in the previous example, the pool does not give any permissions to Red Hat Enterprise Linux Server. The exact details of the subscriptions you see will likely differ from the example above.
Each of these permissions gives access to different program channels (YUM repositories). Not all permission repositories are required for Red Hat Virtualization Manager. You should disable all software repositories on your server, and then only enable the ones that are needed.
Disable all existing repositories:
[email protected] ~]# subscription-manager repos –disable=*
Add the required repositories:
[email protected] ~]# subscription-manager repos
The required repositories include the following software:
|rhel-7-server-rpms||Red Hat Enterprise Linux 7 Server Packages|
|rhel-7-additional-server-rpms||Optional Red Hat Enterprise Linux 7 packages, including a supported version of the Java Runtime Environment (JRE) and the virtio-win package.|
|rhel-7-server-rhv-4.1-rpms||Red Hat Virtualization Manager 4.1 Basic Packages|
|rhel-7-server-rhv-4-tools-rpms||Additional Red Hat Virtualization 4 tools, including virt-v2v|
|jb-eap-7-for-rhel-7-server-rpms||JBoss Enterprise Application Platform 7 packages|
Finally, use yum to update all packages on your system to the latest versions:
[email protected] ~]# yum -y update
Step 2: Installing Red Hat Virtualization Manager software
After installing the operating system and enabling the required software repositories, install the rhevm package and its dependencies using the yum command. The dependencies for the rhevm package ensure that yum loads everything it needs to run Red Hat Virtualization Manager.
[email protected] ~]# yum -y install rhevm
Message: The package used to install Red Hat Virtualization Manager 4.1 is called rhevm by e, and not rhvm as you might expect. This is the brand legacy for Red Hat Enterprise Virtualization 3. The name of the package may change in future junior releases of Red Hat Virtualization. When you install the rhevm package using yum, a number of additional packages are downloaded and installed. It takes about five minutes.
Step 3: Configuring Red Hat Virtualization Manager
Once the installation of the package is complete, perform the initial configuration of Red Hat Virtualization Manager by running engine-setup in a terminal on the server. The engine-setup command interactively requests and applies a set of configuration settings and starts Red Hat Virtualization Manager. You can then log into the administration portal using a web browser to configure the image store and register the hosts on which the virtual machines will run.
The following example covers the settings required for a typical standalone installation of Red Hat Virtualization Manager on a bare metal server for production use.
Start the installation process by running engine-setup as root.
[email protected] ~]# engine-setup
The engine configuration process asks questions about how Red Hat Virtualization Manager should be configured. It provides default settings for most problems. These default values are enclosed in square brackets ([ and ]). Press the Enter key to accept the default value or manually enter another value.
The engine-setup command first asks for information about the product parameters.
–== PRODUCT OPTIONS ==
Configure the engine on this host (Yes, No) [Yes]:
Configure the I/O image proxy on this host? (Yes, No) [Yes] :
Configure WebSocket proxy on this host (Yes, No) [Yes]:
Configure data storage on this host (Yes, No) [Yes]:
Configure VM console proxy on this host (Yes, No) [Yes]:
Tick [Yes] at the end of each question. This is the default value. The default settings in this section configure a number of important services on the Red Hat Virtualization Manager master node:
- The main mechanism of Red Hat Virtualization Manager.
- Image I/O proxy that downloads images to storage domains.
- WebSocket proxy that supports noVNC or SPICE HTML5 connections to virtual machine consoles.
- A data warehouse that supports the full operations management database of Red Hat Virtualization. Installing Data Warehouse on the RHVM server is easy, but it can also be installed on a separate database server to reduce the load on the system.
- VM Console Proxy, which publishes serial console access to virtual machines through the SSH service running on port 2222 of the Red Hat Virtualization Manager server.
The Network Configuration section queries the DNS server name and confirms that the DNS name resolution is working forward and backward. You will also be asked if you want the firewall ports required by Red Hat Virtualization Manager to be automatically opened by the firewall system.
–== NETWORK CONFIGURATION ==
The full DNS hostname of this server is [rhvm.lab.example.com] :
The installer can automatically configure the firewall on this system.
Message: The automatic firewall configuration can override the current
Do you want the installer to configure the firewall? (Yes, No) [Yes] :
INFO] firewalld is configured as a firewall manager.
In the Database Configuration section, you are prompted to configure the PostgreSQL database used for the data warehouse. In the following example, the data warehouse database is configured on the local RHVM server that is used by default.
–== DATABASE CONFIGURATION ==
Where is the DWH database located? [Local, remote] [Local]:
The installation can automatically configure the local Postgresql server to run
DWH. This can lead to conflicts with existing applications.
Do you want the setup to automatically configure postgresql and
to create a DWH database, or would you rather do it manually? (Auto, Manual)
Where is the engine database? [Local, remote] [Local]:
The installation can automatically configure a local postgresql server running the
engine. This can lead to conflicts with existing applications.
Do you want the installer to automatically configure postgresql and
to create the engine database, or would you rather do it manually? (Auto, Manual)
The oVirt Engine Configuration section defines the default password for the admin user in the internal authentication area. Don’t forget the password, as you will need it later to log into the administration portal to configure storage, VM hosts, and other users.
If you specify a weak password, engine-setup warns you and asks you to confirm that you want to use this password. Since the admin user has full administrative access to Red Hat Virtualization Manager, it should have a strong password and should only be used if the admin user’s personal account is not working or not yet configured.
You will also be asked which operating mode the motor should operate in. These two options are the most flexible and should be chosen in general. In this mode, Red Hat Virtualization Manager can manage GlusterFS storage pools and use GlusterFS as a data domain to host disks for virtual machines.
–== OVIRT ENGINE CONFIGURATION ==
Engine administrator password: …password…
Confirm the password of the motor administrator: …password…
Application mode (Virt, Gluster, Both) [Both]:
Under Storage Configuration, the default SAN wipe after delete setting is a security setting that deletes virtual disk blocks when a virtual machine is deleted. This function is disabled by default.
–== MEMORY SETTINGS ==
Default SAN DELETE after DELETE (Yes, No) [No]:
The PKI Configuration section specifies the organization name used in the TLS certificate for the server.
–== PKI CONFIGURATION ==
Organization name for certificate [lab.example.com]:
The Apache Configuration section installs the Apache HTTPD web server used by Red Hat Virtualization Manager. When the application is installed as the default web server page, the web server home page becomes the landing page with links to the Red Hat Virtualization Manager login screen, documentation, and other resources. Normally this should be fine, as you should not be running any other applications on this web server.
You are also asked whether you want to set up an HTTPS certificate with a certificate authority (CA) within Red Hat Virtualization Manager or with a certificate from an external CA.
–== APACHE CONFIGURATION ==– The
installation can configure the default web server page as the home page for the
application. This can lead to conflicts with existing applications.
Do you want to set the application as default page on the
web server? (Yes, No) [Yes] :
This setting allows you to configure Apache to use SSL with a certificate issued by an internal
Do you want the installer to configure it, or do you prefer to do it manually?
(Automatic, Manual) [Auto] :
In the System Configuration section, you are asked if you want to configure Red Hat Virtualization Manager to provide NFS exports for use as an ISO domain. This is only suitable for the test version or a very small test environment. In a production environment, it makes sense to use a dedicated NFS server or storage appliance. The default setting is None.
–== SYSTEM CONFIGURATION ==
Configure the NFS share on this server to be used as an ISO domain? (Yes,
There are two sample scales available for Red Hat Virtualization Manager Data Warehouse: Basic and complete. The default setting is Basic. Full registration of more detailed data, but it also requires more storage in the database and can increase the load on the database.
–== MIS CONFIGURATION ==
Select the data warehouse sample size:
(1, 2)  –== END OF CONFIGURATION ==
This completes the configuration settings and engine-setup begins to verify the installation.
In the configuration check phase, all configuration parameters specified so far are checked and a summary of the configuration parameters is printed for confirmation. If you notice an incorrect setting in the configuration preview window, cancel the setting by typing Cancel, or type OK if everything is correct.
INFO] Step : Installation check
[WARNING] Less than 16384 MB available memory
–== CONFIGURATION CHECK ==
Application mode: both
By default, the SAN is cleared after deletion: False
Firewall Manager: firewalld
Update firewall : True
Host FQDN: rhvm.lab.example.com
Configure local engine database: True
Set application as default page : True
Configuring Apache SSL : True
Secure connection to the motor database : False
Engine database username: engine
Engine database name: engine
Engine database host: localhost
Engine database port: 5432
Check the Host Name of the Engine Database : Improper engine installation
PKI organization: lab.example.com
DWH configuration: True
DWH Secure database connection : False
DWH Database Host: localhost
DWH Database Username: ovirt_engine_history
DWH Database Name: ovirt_engine_history
DWH Database Port: 5432
Check the host name of the DWH database : False
DWH Local Database Configuration : True
Setting the image input/output proxy : Where
Configure the VMConsole proxy server : True
WebSocket proxy configuration : The Truth
Confirm the installation settings (OK, Cancel) [OK] : OK
Message: If less than 16 GB of memory is available, a warning is displayed as in the previous example. For a small environment, like the one used in this course, we can safely ignore this warning. However, for medium to large production environments with many active hosts and virtual machines, 16 GB or more of system memory is recommended.
This step configures and starts Red Hat Virtualization Manager. A number of information messages are displayed on the terminal.
When the installation and start of the service is successful, engine-setup displays a message similar to the following and ends:
== SYNC, CORRECTED BY ELDERMAN ==
INFO ] Restart httpd
Use the user ‘[email protected]’ and the specified password to log in
Web access is allowed at:
Internal CA CC:C6:8A:2A:66:30:17:10:21:1E:52:20:B3:6A:D2:A2:22:7A:E9:89
SSH fingerprint: 9f:8b:65:cf:37:b4:45:ca:22:3e:31:09:60:c9:64:d2
[WARNING] Less than 1,638.4MB of available memory.
== SYNC, CORRECTED BY ELDERMAN ==
INFO] Step : Cleanup
The log file is located in /var/log/ovirt-engine/setup/ovirt-engine-
[ INFO ] Creating the response file ‘/var/lib/ovirt-engine/setup/
[ INFO ] Stage : Intermediate completion
[ INFO ] Step : Completed
[ INFO ] Installation completed successfully
[[email protected] ~]#
If the installation does not complete successfully, the summary shows the location of the log file in /var/log/ovirt-engine/setup. This log file is the first source of information in case something goes wrong during the configuration process.
The summary also tells you where to find the landing page for your Red Hat Virtualization Manager installation. In this example, it’s https://rhvm.lab.example.com/ovirt-engine. If you specify that the application should be set as the default page on the web server, the default host URL will also work. In the example above, the URL https://rhvm.lab.example.com also leads to this landing page.
Access to the management portal
Red Hat Virtualization Manager has a number of interfaces that allow you to interact with and manage your Red Hat Virtualization environment. Some of these are provided by the Apache httpd web server. One of the main interfaces accessible from the Red Hat Virtualization Manager landing page is the administration portal. This cross-platform web interface is accessible through any supported web browser.
Login management portal
To access the administration portal, open a web browser and enter the URL of the landing page as described in the previous section. Click on the link to the management portal. You can also access the management portal directly at https://your-rhvm-server-fqdn/ ovirt-engine/sso/login.html.
If you do this, your web browser may start complaining because it does not recognize the certificate authority that signed the TLS certificate for the Red Hat Virtualization Manager web server. There are three ways to solve this problem:
1. First, you can download the certificate from the local CA and install it in your web browser. It is available at http://your-rhvm-server- fqdn/ovirt-engine/services/pki-resource?resource=ca-certificate&format=X509-PEM-CA (replace your-rhvm-server-fqdn with the full domain name of your RHVM server).
2. Second, you can replace the TLS certificate used by the server with one signed by a CA that your web browser already trusts. At the time of this writing, instructions on how to do this are included in Appendix D, Red Hat Virtualization and SSL, of the Red Hat Virtualization 4.1 Administration Guide at https://access.redhat.com/. (The exact location of these instructions may change in a future revision of the documentation).
3. Finally, you can add a security exception to your web browser to accept the self-signed certificate as valid. For Firefox, the procedure to follow from the error page is as follows:
- Click on the Advanced button.
- Click the Add Exception button.
- Click the Confirm Security Exception button in the Add Security Exception dialog box.
On the landing page, under Portals, click Administration Portal to be redirected to the Administration Portal login page. You can also access the management portal directly by going to https://your-rhvm-server-fqdn/ovirt-engine/sso/login.html.
To log in to the portal for the first time, log in with the user admin and the password defined in engine-setup. The profile must be defined as internal to use the internal authentication domain.
After successfully logging in, you will be taken to the management portal dashboard.
install red hat virtualizationrhv 4.4 installation guideredhat documentsred hat virtualization overviewrhv 4.4 betared hat virtualization manager installation,People also search for,Privacy settings,How Search works,red hat virtualization manager installation,red hat virtualization installation step by step,install red hat virtualization,rhv 4.4 installation guide,redhat documents,red hat virtualization overview,business benefit of red hat virtualization,rhv 4.4 beta