Red Hat Virtualization (RHV) Reviews & Insights

We are using RHEV for the virtualization of servers in our environment. Currently, we are using RHEV for nonproduction servers. The best part of RHEV is an open source product in virtualization technology, it is vendor-independent software and a lot more cost-effective and flexible than proprietary solutions. We are managing 100 plus Virtual machines with RHEV in our environment and using the hardware efficiently as well as saving the cost of our project.

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 used to host virtual machines for our telecommunications applications.

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.

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.

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.

We have many servers in our organization running Linux. We have hosted many virtual machines on the same, and many of the company applications are running on those VMs resulting in a cost-effective solution as well as time-saving as it reduces the need for hardware every time our company has IT needs.

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.

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.

It's currently being used across the organization - it includes all the enterprise-grade features for a less overall TCO as compared to something like VMware's offerings. It's easy to use, manage, and provision and has rock-solid reliability. It's backed with the best support in the industry and uses KVM Virtualization under the hood which is used all throughout the industry by some of the top names (AWS and Rackspace to name a couple).

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.

I am working as a Consultant, so I usually advise other companies in terms of virtualization solutions and implement them.

RHEV is usually used at our customers for providing an open-source based virtualization stack which is very similar to virtualization systems they already have (e.g. libvirt and KVM nodes). Therefore the learning curve is really low when RHEV is introduced to them.

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.

We use RHEV across the organization from RND all the way down to our customer support operations. Every level has their own requirements and expectations from software and its use, RHEV provides the organization with a scalable virtualization platform that answers more of todays needs than competitors. We host systems for companies wanting a cloud based solution and the performance from RHEV is right on par with what our needs are.

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.

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.

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 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.

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.