Red Hat cranks virtualization power play

Move aside, Microsoft, Citrix, VMware...


Red Hat is a player in operating systems and middleware, and it wants to be a player in server virtualization - at least more of a player than it has been since it parked the Xen hypervisor inside its Enterprise Linux 5 distro back in March 2007.

The company has been dropping hints about its plans for server and desktop virtualization since acquiring Qumranet, the creator of the KVM virtualization hypervisor, for $107m in cash last September. After last week announcing an interoperability agreement with Microsoft, which will see Red Hat support Windows instances atop its Xen and KVM hypervisors and Microsoft support RHEL atop its Hyper-V hypervisor, and ahead of VMware's VMworld Europe trade event in Cannes, which starts tomorrow, Red Hat decided it had better explain what it was going to do with KVM.

And so Red Hat today mapped out its server and desktop virtualization plans, which are going to take the next 18 months to get fleshed out with some details and delivered as commercialized products.

"Red Hat is in a power position to set the agenda for virtualization," said Brian Stevens, chief technology officer at the Linux outfit, which is also - by virtue of its JBoss acquisition - one of the key providers of middleware.

Stevens didn't say much on the call except that the broad product offerings would be called Red Hat Enterprise Virtualization and that the company was partnering with chip maker Intel and server maker IBM to bring this KVM-based technology to market. IBM's help seems to be related exclusively to the delivering of virtualization for Linux as it relates to its x64, Power, and mainframe servers.

Red Hat invested more than a year to get the open source Xen hypervisor embedded inside RHEL 5, a project that was announced in November 2005 for delivery in late 2006, but which was pushed out by about six months to March 2007 because Xen was such a moving target back then.

Last year, Red Hat opted to go with KVM because unlike Xen, KVM is part of the mainstream Linux kernel, which means developers are not constantly trying to reconcile the Linux kernel and the Xen hypervisor. (That's why Qumranet is worth $107m in cash, and why Citrix Systems and the open source Xen community it sponsors should try to get Xen mainstream as well.)

And that is why Red Hat is going to be basing its future virtualization strategy on KVM. Consider Xen part of the learning experience and something that Red Hat is happy to support in RHEL 5 as long as customers want to use it.

But starting with RHEL 5.4, KVM will be the default hypervisor inside RHEL not Xen, according to Navin Thadani, senior director of the virtualization business at Red Hat. (This shift is already under way with the Fedora development release of Linux. Fedora 10, which came out in November last year, has both Xen and KVM hypervisors, but Fedora 11, due at the end of May, will default to KVM. The default position on installation is not just a matter of preference, but a signal that KVM will be ready for primetime.

Next page: Inaugural KVM

Similar topics


Other stories you might like

  • Prisons transcribe private phone calls with inmates using speech-to-text AI

    Plus: A drug designed by machine learning algorithms to treat liver disease reaches human clinical trials and more

    In brief Prisons around the US are installing AI speech-to-text models to automatically transcribe conversations with inmates during their phone calls.

    A series of contracts and emails from eight different states revealed how Verus, an AI application developed by LEO Technologies and based on a speech-to-text system offered by Amazon, was used to eavesdrop on prisoners’ phone calls.

    In a sales pitch, LEO’s CEO James Sexton told officials working for a jail in Cook County, Illinois, that one of its customers in Calhoun County, Alabama, uses the software to protect prisons from getting sued, according to an investigation by the Thomson Reuters Foundation.

    Continue reading
  • Battlefield 2042: Please don't be the death knell of the franchise, please don't be the death knell of the franchise

    Another terrible launch, but DICE is already working on improvements

    The RPG Greetings, traveller, and welcome back to The Register Plays Games, our monthly gaming column. Since the last edition on New World, we hit level cap and the "endgame". Around this time, item duping exploits became rife and every attempt Amazon Games made to fix it just broke something else. The post-level 60 "watermark" system for gear drops is also infuriating and tedious, but not something we were able to address in the column. So bear these things in mind if you were ever tempted. On that note, it's time to look at another newly released shit show – Battlefield 2042.

    I wanted to love Battlefield 2042, I really did. After the bum note of the first-person shooter (FPS) franchise's return to Second World War theatres with Battlefield V (2018), I stupidly assumed the next entry from EA-owned Swedish developer DICE would be a return to form. I was wrong.

    The multiplayer military FPS market is dominated by two forces: Activision's Call of Duty (COD) series and EA's Battlefield. Fans of each franchise are loyal to the point of zealotry with little crossover between player bases. Here's where I stand: COD jumped the shark with Modern Warfare 2 in 2009. It's flip-flopped from WW2 to present-day combat and back again, tried sci-fi, and even the Battle Royale trend with the free-to-play Call of Duty: Warzone (2020), which has been thoroughly ruined by hackers and developer inaction.

    Continue reading
  • American diplomats' iPhones reportedly compromised by NSO Group intrusion software

    Reuters claims nine State Department employees outside the US had their devices hacked

    The Apple iPhones of at least nine US State Department officials were compromised by an unidentified entity using NSO Group's Pegasus spyware, according to a report published Friday by Reuters.

    NSO Group in an email to The Register said it has blocked an unnamed customers' access to its system upon receiving an inquiry about the incident but has yet to confirm whether its software was involved.

    "Once the inquiry was received, and before any investigation under our compliance policy, we have decided to immediately terminate relevant customers’ access to the system, due to the severity of the allegations," an NSO spokesperson told The Register in an email. "To this point, we haven’t received any information nor the phone numbers, nor any indication that NSO’s tools were used in this case."

    Continue reading

Biting the hand that feeds IT © 1998–2021