Is Red Hat the New VMware?

khess 0 Tallied Votes 964 Views Share

Red Hat Enterprise Linux now comes with built-in virtualization (KVM) but is Red Hat Enterprise Virtualization (RHEV) about to go to the virtual mat with VMware? If you look at their , you'll come away with a resounding 'Yes' to that question.

Red Hat purchased Qumranet in 2008 to acquire their KVM-based virtualization solution and SolidICE product based on the SPICE protocol.

What does RHEL mean for consumers?

For the end user, folks like you and me, it means that hosting companies can offer more services to developer and companies that host their applications at third-party locations, which in turn means richer applications and experiences. It also means lower costs because adopters can implement Red Hat's enterprise virtualization solution without the high upfront costs associated with established virtualization technologies.

What does RHEL mean for corporate adopters?

Smart CIOs will see the writing on the wall and engage Red Hat's virtualization team to migrate their physical servers to virtual ones. Lower and predictable costs are just two of RHEL's advantages over other Linux-based virtualization solutions. KVM is a full virtualization solution, like VMware or Citrix, but has the distinct advantage of the super fast SPICE protocol.

The primary question remains, "Is Red Hat the new VMware?" There's a good chance that it is. Red Hat dominates the commercial Linux market and that fact places it in a strategic position to launch itself into a head-to-head competitive grapple with VMware. VMware's market advantages are that it has years of domination and it's alliance with Cisco makes it a formidable force in the virtualization space.
Red Hat has its work cut out for it in competing with VMware on its turf but VMware should keeps its eyes on Red Hat.

Dani AI

Generated

raised the right question for 2010; was also right that enterprises picked up Red Hat's virtualization work early. The fight did not become a simple one-vs-one replacement. Two big shifts changed the playing field: Red Hat joined IBM’s hybrid-cloud strategy when IBM closed its acquisition of Red Hat in July 2019, and Red Hat invested heavily in containers and Kubernetes technologies in the years before that. (redhat.com)

Technically, the stack matured. The community virtualization manager oVirt serves as the upstream for Red Hat’s virtualization tooling, and KVM is now a first-class, in-kernel hypervisor with a stable API used in many production environments. At the same time, Kubernetes and cloud-native patterns moved many new workloads away from traditional VM-first designs. Those trends reshaped how organizations choose between vSphere-style stacks, KVM/oVirt/RHV, and container platforms. (ovirt.org)

Short, practical checklist for modern planning:

  • Inventory workloads and classify by statefulness, latency, and hardware needs.
  • Run a small PoC: test live migration, storage performance, and backup/restore under load.
  • Validate management and automation needs (APIs, Ansible/OpenShift integration).
  • Confirm support, SLAs, and toolchain compatibility (some VMware features are proprietary).
  • Treat containers as a parallel strategy for new, cloud-native apps; keep VMs for legacy/stateful services.

Framing: Red Hat became a credible enterprise alternative for many use cases, but the bigger shift since 2010 is that infrastructure choices widened — not simply Red Hat replacing VMware. The right answer depends on workload profile, support expectations, and a concrete migration plan.

DimaYasny 180 Godmode enabled Team Colleague Featured Poster

RHEV has already been adopted by several major players, including IBM. So this is old news, the "new" news is the recent RH summit, and the GA release of RHEV 2.2

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.