Skip to main content
TrustRadius
Red Hat Virtualization (RHV)

Red Hat Virtualization (RHV)
Formerly RHEV

Overview

What is Red Hat Virtualization (RHV)?

Red Hat Virtualization (formerly Red Hat Enterprise Virtualization, broadly known as RHEV) is an enterprise level server and desktop virtualization solution. Red Hat Virtualization also contains the functionality of Red Hat Enterprise Virtualization for Desktop in later editions of the…

Read more
Recent Reviews

Make way for RHEV

10 out of 10
February 23, 2016
Incentivized
RHEV is used as a one stop solution for virtual environments due to it being part of the RedHat distro.
Business problems that come with …
Continue reading
Read all reviews

Popular Features

View all 5 features
  • Virtual machine automated provisioning (10)
    7.9
    79%
  • Management console (10)
    7.3
    73%
  • Live virtual machine backup (9)
    7.3
    73%
  • Live virtual machine migration (10)
    6.9
    69%
Return to navigation

Pricing

View all pricing

Standard

$999.00

Cloud
Per Year Per Hypervisor

Premium

$1,499.00

Cloud
Per Year Per Hypervisor

Entry-level set up fee?

  • No setup fee

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services
Return to navigation

Product Demos

Integrated, unified container and VM management with RHV and OCP

YouTube

V2V converts systems to KVM (demo)

YouTube
Return to navigation

Features

Server Virtualization

Server virtualization allows multiple operating systems to be run completely independently on a single server

7.7
Avg 8.3
Return to navigation

Product Details

Red Hat Virtualization (RHV) Integrations

Red Hat Virtualization (RHV) Technical Details

Deployment TypesSoftware as a Service (SaaS), Cloud, or Web-Based
Operating SystemsUnspecified
Mobile ApplicationNo

Frequently Asked Questions

Red Hat Virtualization (formerly Red Hat Enterprise Virtualization, broadly known as RHEV) is an enterprise level server and desktop virtualization solution. Red Hat Virtualization also contains the functionality of Red Hat Enterprise Virtualization for Desktop in later editions of the platform.

Reviewers rate Hypervisor-level security highest, with a score of 8.9.

The most common users of Red Hat Virtualization (RHV) are from Mid-sized Companies (51-1,000 employees).
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(33)

Reviews

(1-5 of 5)
Companies can't remove reviews or game the system. Here's why
Score 5 out of 10
Vetted Review
Verified User
Incentivized
Red Hat Virtualization is used to host virtual machines for our telecommunications applications.
  • 1- It easy to upload qcow2 images from the browser.
  • 2- It is easy to automate repetitive tasks with Ansible using RHVM API.
  • 3- It is easy to patch the hypervisors.
  • 1- RHVM API is pretty slow, especially after creating a VM it is not possible to retrieve the VM details (i.e VM's MAC Address) fast enough, where we need to place a pause in our Ansible Playbook, make the automation process slow.
  • 2- RHV is still using collected to monitor the hypervisors which is deviating from Red Hat policy for other RHEL based applications to use PCP to monitor, which is richer in features.
  • 3- It will be great if it is possible to patch the hypervisors using other tools such as satellite and not only via RHVM.
  • 4- In the past Red Hat used to present patches in the z release (i.e. 4.3.z), and features in the y release (i.e 4. y), but starting from 4.4 that is mixed together wherein the Z release you get both patches and features, that is not good because that requires a lot of time to test when we patch as it includes features as well.
  • 5- Engineering team has to be more reactive when new feature is requested.
Red Hat Virtualization is suitable for small implementation and hosting VMs. However, when you start asking for additional features or enhancements, the engineering team is not the flexible as other engineering teams in Red Hat. It is very likely they will not accept adding features or in the best case. They wouldn't commit to a plan when it is possible to be available.
  • 1- Automating regular tasks using Ansible.
  • 2- Deploying VMs using templates.
  • 3- Special features for VMs as CPU pinning and NUMA.
Server Virtualization (5)
76%
7.6
Virtual machine automated provisioning
80%
8.0
Management console
80%
8.0
Live virtual machine backup
60%
6.0
Live virtual machine migration
60%
6.0
Hypervisor-level security
100%
10.0
  • 1- The subscription fees is relatively low compared to other virtualization solutions.
  • 2- Automation of VMs' deployment is simple, that helped a lot in speeding up VM deployment however there is room to improve by making the API faster.
  • 3- Adding hypervisors in an automated way is simple that helped to scale out our environment.
RHV has the following advantages:
  • They have relatively cheaper subscriptions compared to others.
  • With the future going to Openstack and containerization migrating to KVM-based virtualization will be easier to migrate to future products.
  • The easiness to use Ansible to automate activities on Red Hat Virtualization make it easier to consolidate all your automation tasks using one automation solution.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
Due to its inclusion in RedHat, RHV is utilized as a one-stop solution for virtual environments. The installation expenses of such a system pose a significant challenge for businesses. We're utilizing RHV instead of VSphere since it's more cost-effective and easier to integrate with KVM.
  • RHV issues/bugs can be reported via Bugzilla to RH support. The service is great and typically responds soon.
  • Red Hat distribution integration is seamless as it is integrated into the kernel.
  • OpenStack support enables more customized VM templates and network configuration control.
  • If the aforementioned can't be done, additional open-source tool compatibility or support.
When it comes to managing virtual machines, RHV is the best choice. RHV is a good option if you deal with OpenStack, as it has built-in support for it. In this case, you may not be able to justify the expense. However, adopting something like oVirt (which is related to but not identical to RHV) might be preferable despite the fact that oVirt is not built into the kernel.
  • Improved compatibility with KVM.
Server Virtualization (5)
90%
9.0
Virtual machine automated provisioning
90%
9.0
Management console
80%
8.0
Live virtual machine backup
90%
9.0
Live virtual machine migration
90%
9.0
Hypervisor-level security
100%
10.0
  • Testing on oVirt before acquiring RedHat service contracts has a positive influence.
Compared to oVirt, RHEV is more stable but has fewer capabilities. ESX is far more difficult to automate.
Emile Swarts | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User
Incentivized
This was used in an organisation which I was working for, using a client-server architecture. This led to a more consistent environment and prevented *snowflake* desktops, which could be hard to diagnose issues on and provide support for. This also increased security and ultimately ended up saving a significant amount money for the company.
  • Standardisation where provisioning the environment became repeatable and predictable.
  • Easier debugging and understanding the client system.
  • Improved security and centrally managed.
  • Ran into a regression when updating firmware for IGEL
  • Desktop froze and became non responsive on a few occasions.
  • Server crashed and took down all the clients in the Thin setup.
  • Well suited for very large organisations with a wide variety of departments.
  • Less useful for a single group of developers where the command line is mostly used.
  • Positive effect in that it saves money on support and debugging client machines.
  • Faster to fix bugs and debug user issues.
  • Amazon WorkSpaces
  • Red Hat Enterprise is more expensive but better supported when it comes to support.
  • Amazon WorkSpaces had more online documentation and resources to scan through.
Charles Inglese | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User
Incentivized
RHEV is being used to implement an open-source hypervisor (KVM) with an easy-to-use front end for our customers. Our organization is exploring the feasibility of using it to deploy to multiple external locations in order to make management of VMs easy for remote administrators. It has a very well documented Python API, which makes automation easier to implement.
  • Automation integration
  • Migration of VMs from one physical host to another
  • Support for open-source community projects, such as Gluster, Cinder, and Glance
  • Product Q&A, regression testing, bug fix turnaround
  • Standardization of deployment between the baseline products (e.g. stand-alone vs. appliance should support same configuration options)
  • Improve WebUI navigation
Red Hat Enterprise Virtualization (RHEV) is well suited for environments where skilled Linux/Python engineers are available to help configure, install, and deploy it. The majority of the back-end of the product is written in Python and when issues arise, engineers will need to parse log files generated by Python. It is not well suited for Microsoft Windows only shops.
Server Virtualization (5)
82%
8.2
Virtual machine automated provisioning
60%
6.0
Management console
70%
7.0
Live virtual machine backup
90%
9.0
Live virtual machine migration
90%
9.0
Hypervisor-level security
100%
10.0
  • Reduced COTS costs to our organization due to the fact that it is open-source and has a freely available version (oVirt)
  • It has helped to bring technology quickly to our operational locations due to the ability to quickly automate and deploy it
  • It has enabled increased security to our enterprise due to the fact that it supports SELinux and allows us to customize the security posture of the infrastructure more easily
VMware ESXi is a more mature technology, as it has been around for a longer period of time. However, automating ESXi installations requires hacking OEM media and an intense amount of knowledge of how ESXi operates under the hood. The WebUI and associated functionality for ESXi is more stable than RHEV, however ESXi does not support open-source community projects such as Gluster, Cinder, or Glance natively and relies on HW RAID, NAS, or SAN to achieve high availability. Additionally ESXi licenses tend to be more expensive than using RHEV or it's freely available sibling oVirt.
February 23, 2016

Make way for RHEV

Score 10 out of 10
Vetted Review
Verified User
Incentivized
RHEV is used as a one stop solution for virtual environments due to it being part of the RedHat distro.
Business problems that come with this is the costs associated with the implementation of such a solution.
  • Any issues/bugs with RHEV can be fixed by using bugzilla to get in contact with RH support. The support is fantastic and a reply is usually given fairly quickly.
  • Integration into RedHat distro is seamless as it is already baked into it's kernel.
  • Support for OpenStack allows for more customization with VM templates and advanced network configuration management.
  • I would like to see more cloud automated solutions with RHEV with kickstarting nodes without external assistance with tools such as cobbler/foreman.
  • If the above cant be done, then more compatibility or support for other open source tools.
RHEV is most suited in any situation that requires VM management. If you work with openstack then using RHEV would be something to look at since it does have support for it.
It might be less appropriate if you are just needing to save cost. However, using something like oVirt (similar if not the same as RHEV) would be better even though it would take a little more work to use oVirt as oVirt is not baked into the kernel.
Server Virtualization (5)
86%
8.6
Virtual machine automated provisioning
80%
8.0
Management console
90%
9.0
Live virtual machine backup
100%
10.0
Live virtual machine migration
70%
7.0
Hypervisor-level security
90%
9.0
  • Negative impact due to costs associated with the service contract as we are switching to oVirt due to cutting costs.
  • Positive impact is that testing on oVirt before purchasing service contracts with RedHat can be done.
Pretty much Open Source sums it up.
Return to navigation