Red Hat Virtualization (RHV)

Formerly RHEV

RHEV is well suited for organizations that need a cost-effective and flexible solution for their environment. As its vendor-independent software, easily install on any type of hardware. RHEV provides a GUI interface to manage the software, which makes the management of the software easier for the end-user. RHEV is best for non-production or less critical applications. RHEV can be easily integrated with other REDHAT software.

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.

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.

If any organization wants to run many many apps with minimal hardware and minimum costing, then it is the best solution. There is no extra cost involved, it comes free with Linux and is open source. If given proper training one or two times, it is easy to install and use as well.

If you're looking for a reliable open-source VDI solution then this maybe the product for you and your organization, the live migration and exceptional end user experience are really well done. Its other features such as USB support, efficient desktop pooling, snapshot features, load balancing and many more are implemented in its competitors as well but are better managed here in my honest opinion.

I believe it's an excellent solution for any scenario which requires virtualization. The only scenario where it might not be the best solution would be in building out a cloud infrastructure - you could certainly integrate RHEV for something like that but I think that either OpenStack or CloudStack might be a better solution for building cloud environments.

Red Hat Enterprise Virtualization is well suited for IT departments which use open-source software already and want to rely on an enterprise virtualization solution which is very similar to the tools they already know.

In addition, RHEV fits in very well to environments already containing other products from Red Hat.

IT departmens with high performance needs should avoid RHEV in some scenarios.

Red Hat Enterprise Virtualization has provided the flexibility we need to offer a highly reliable and scalable cloud solution to our customers. As one of the leading security providers in the world, Red Hat Enterprise Virtualization will deliver unparalleled experience to our customers as we embark on a new shift in operations. Our organization has just shifted focus to provide a more robust offering and we were not able to do so without RHEV. There are still some instances where vmware has redhat beat purely due to their maturity in the space.

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.

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.

Well suited for a Linux based deployment utilizing KVM and needing a web interface. Most useful for people wanting to use an API to act against the hypervisor