Skip to main content

Redhat's KVM provides better consolidation ratio than VMware ESX

At a journalists' roundtable in London this week, Benny Schneider, Qumranet CEO, said his - now Red Hat's - company's KVM (kernel-based virtualisation machine) hypervisor runs 52 VMs in a physical server, in which ESX can host a maximum of 35 VMs. Citrix Xenserver is worse: it can only host 30.

There are two reasons why KVM is better than ESX, according to Schneider.

First, KVM is newer code: when it started being designed four years ago Intel and AMD were already extending their processor instruction sets to add virtualization-supporting instructions. Early hypervisors like ESX had to cope with the previous generation of CPU chips, which had no virtualisation support, and so were larger and made less efficient use of server resources.

In other words, VMware is held up by legacy code baggage, and Qumranet is not, or so Red Hat says.

Second, Windows needs lots of memory and is a bulky VM in RAM terms, according to Schneider. He hinted that KVM can reduce this Windows VM memory burden, freeing up RAM for other VMs.

Qumranet also provides Red Hat VDI (virtual desktop infrastructure) technology, which supports more remote desktops and gives the users a better experience because of its SPICE rendering technology. It compresses the desktop data stream better and enables a Linux server to be a better Windows VDI host than a VMware or Citrix Xenserver server. Red Hat CTO Brian Stevens acknowledged that it's a little odd that Red Hat's desktop strategy is now focused on the virtualized Windows desktop.


El Reg reporting here

Comments

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus

Splunk that!

Saw this advert on Slashdot and went on to look for it and found the tour pretty neat to look at. Check out the demo too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op

Virtualization is hot and sexy!

If this does not convince you to virtualize, believe me, nothing will :-) As you will hear these gorgeous women mention VMware, Akkori, Pano Logic, Microsoft and VKernel. They forgot to mention rackspace ;-) virtualization girl video I'm convinced, aren't you? Check out their site as well!