Kernel-based Virtual Machine (KVM) is a virtualization solution developed by small Israeli software company Qumranet and supported by Red Hat since that company's acquisition in 2008.
N/A
Red Hat OpenShift
Score 9.3 out of 10
N/A
OpenShift is Red Hat's Cloud Computing Platform as a Service (PaaS) offering. OpenShift is an application platform in the cloud where application developers and teams can build, test, deploy, and run their applications.
N/A
Pricing
Kernel-based Virtual Machine (KVM)
Red Hat OpenShift
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
KVM
Red Hat OpenShift
Free Trial
No
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Kernel-based Virtual Machine (KVM)
Red Hat OpenShift
Considered Both Products
KVM
Verified User
Anonymous
Chose KVM
Kernel-based Virtual Machine is an open-source and free solution, compared to Virtualbox which is a product from Oracle.
The key points why I made my decision for KVM in comparison with VMWare are: Freeware software (I am using an Ubuntu server OS), Fewer resources usage, vSwitch using that provides the ability to configure dot1q trunks to/between VMs, Stability, and simplicity of …
Compared to VirtualBox, KVM has simpler licensing terms and is supported by the operating system vendor. KVM also has more mature integrations with other open-source projects. Automating provisioning is simple with KVM since it is available in the package repositories of …
KVM is free and provides environments where guests can run their own Kernel while still performing very well. It is also very native to work with KVM since it is integrated within the Linux Kernel.
It is a very reliable solution that can be used for x86 architecture virtualization with low overhead. It is a free and open source software. Easy to use withOpenStack.
We've found KVM to be less problematic, both from a stabilty standpoint, but also in a flexibility and licensing standpoint. We love being able to deploy the hardware we want, as we want it, without needing the blessing of a specific vendor.
Nothing like OpenShift. Actually, this was our first one. We toyed with maybe doing raw Kubernetes, but with an enterprise company you need an enterprise product.
Comparing the 2, open source Kubernetes is quicker to setup by about 75%, less restrictive, and free of course, but it lacks the security and support of Red Hat, and deploying features is much harder compared to with operators. For buisiness purposes, OpenShift is just more …
Even though Red Hat OpenShift has more overhead than many other Kubernetes flavors, we have selected Red Hat OpenShift because of it's focus on Security and because of it's excellent vendor support.
Red Hat OpenShift has a better security posture than EKS. I enjoy the console on Red Hat OpenShift more as well. I believe there is greater observability for Red Hat OpenShift.
The Tanzu Platform seemed overly complicated, and the frequent changes to the portfolio as well as the messaging made us uneasy. We also decided it would not be wise to tie our application platform to a specific infrastructure provider, as Tanzu cannot be deployed on anything …
Kernel-based Virtual Machine is very well suited when one needs a single-node virtualization host or needs to build a complex demo setting on their own notebook (e.g. when demonstrating solutions to a customer).
Red Hat OpenShift, despite its complexity and overhead, remains the most complete and enterprise-ready Kubernetes platform available. It excels in research projects like ours, where we need robust CI/CD, GPU scheduling, and tight integration with tools like Jupyter, OpenDataHub, and Quiskit. Its security, scalability, and operator ecosystem make it ideal for experimental and production-grade AI workloads. However, for simpler general hosting tasks—such as serving static websites or lightweight backend services—we find traditional VMs, Docker, or LXD more practical and resource-efficient. Red Hat OpenShift shines in complex, container-native workflows, but can be overkill for basic infrastructure needs.
One thing is the way how it works with the GitHubs model on an enterprise business, how the hub and spoke topology works. Hub cluster topology works the way how there is a governance model to enforce policies. The R back models, the Red Hat OpenShift virtualization that supports the cube board and developer workspace is one big feature within. So yes, these are all some features I would call out.
So I don't know that this is a specific disadvantage for Red Hat OpenShift. It's a challenge for anything that Kubernetes face is. There's an extremely large learning curve associated with it and once you get to the point where you're comfortable with it, it's really not bad. But beating that learning curve is a challenge. I've done a couple presentations on our implementation of Red Hat OpenShift at various conferences and one of the slides I always have in there is a tweet from years ago that said, "I tried to teach somebody Kubernetes once. Now neither of us knows what it is."
This is the current strategy for the company, most of the products in the organisation are aligning to Openshift and various use cases it support. Also lot of applications are being developed for AI use case, openshift.AI provides opportunity to host and leverage the AI capabilities for these applications
It does the job and stays out of the way. The specifics of usability relies on the implementation, but with things like Icarus and libvirt, things are standardizing nicely.
The virtualization part takes some getting used to it you are coming from a more traditional hypervisor. Customization options are not intuitive to these users. The process should be more clear. Perhaps a guide to Openshift Virtualization for users of RHV, VMware, etc. would ease this transition into the new platform
Redhat openshift is generally reliable and available platform, it ensures high availability for most the situations. in fact the product where we put openshift in a box, we ensure that the availability is also happening at node and network level and also at storage level, so some of the factors that are outside of Openshift realm are also working in HA manner.
Overall, this platform is beneficial. The only downsides we have encountered have been with pods that occasionally hang. This results in resources being dedicated to dead or zombie pods. Over time, these wasted resources occasionally cause us issues, and we have had difficulty monitoring these pods. However, this issue does not overshadow the benefits we get from Openshift.
Every time we need to get support all the Red Hat team move forward looking to solve the problem. Sometimes this was not easy and requires the scalation to product team, and we always get a response. Most of the minor issues were solved with the information from access.redhat.com
I was not involved in the in person training, so i can not answer this question, but the team in my org worked directly with Openshift and able to get the in person training done easily, i did not hear problem or complain in this space, so i hope things happen seamlessly without any issue.
We went thru the training material on RH webesite, i think its very descriptive and the handson lab sesssions are very useful. It would be good to create more short duration videos covering one single aspect of openshift, this wll keep the interest and also it breaks down the complexity to reasonable chunks.
The key points why I made my decision for KVM in comparison with VMWare are: Freeware software (I am using an Ubuntu server OS), Fewer resources usage, vSwitch using that provides the ability to configure dot1q trunks to/between VMs, Stability, and simplicity of using/troubleshooting, Well-known interface (for Linux geeks).
We utilized the Thycotic Secret Service to manage all our application secrets, resulting in seamless integration with our applications. We developed all the applications using Red Hat Fuse (currently migrated to Quarkus). We used the built-in Kali Linux support of OpenShift to manage and configure the services and API. Additionally, the Red Hat Developer Studio facilitates faster development.
This is a great platform to deployment container applications designed for multiple use cases. Its reasonably scalable platform, that can host multiple instances of applications, which can seamlessly handle the node and pod failure, if they are configured properly. There should be some scalability best practices guide would be very useful
It has allowed us to see where we need to be in the container world. I'm going to call it a net neutral impact, not negative or positive. It has given us a sense of what we are ready for and what we're not ready for. You know where you stand.
You don't know what you don't know, so it helps us know what we want to know.
