Skip to main content

In KVM's defense

This blogger raises some key issue on KVM. I don't think KVM is all bogus. It definitely has a massive potential. Like any other Virtualization option like rusty's Lguest, Qemu etc. I just wonder about:
  • Interoperability
  • Usability
  • Reliability
  • Production readiness


So why do these companies (and Xensource makes this statement as a company) make such statements? The answer should be not surprising: they have a lot or all to lose. KVM can be the one-in-all solution, unlike any of the others. Xensource and VMWare want to get on your system by providing a hypervisor which then can be used with all kinds of OSes. But: they are in ultimate control. The idea that there suddenly is a virtualization solution which does not need any hypervisor must be absolutely frightening to them. So, they try to suppress this no technology from the start.


Besides anything I also want to mention that innovation is a great thing. I already have Fedora Core 7 test distro and am equally anxious to try out KVM. The whole idea is to make a particular technology relevant and prevalent. Alignment of innovative goals with current consumer needs and demands is what makes a product successful. The world is moving fast. We are into a more "aspirational work and life mode". I want to be able to do things in logical, definite and implementable pieces. And all that today. I need a technology that can help me do that. I need yo use that technology to help me get my message across. It could be any sort of message. Remote management of datacenter, migration of systems, provisioning data centers from anywhere in the world or even a simple demo of the product.

We are all excited about KVM but we also need to see in which context it will be developed, maintained and eventually marketed. After all every technology has to (if it survives the run) reach an inflection point. It has to achieve the "escape velocity".

Check out Ulrich's post.
Labels:

Comments

Post a Comment

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
Post a Comment
Read more

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!
Post a Comment
Read more

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
Post a Comment
Read more