Skip to main content

Linux Virtualization: Can DELL succeed where IBM failed?



Linux Virtualization is coming of age. You have KVM, Xen to name a few. Yet I have to say that the big blue has been on top of this way back in the late 90s and beginning 2000. Whatever happened to the big blue? I have always wondered and when I saw this nd do check out the links provided by the comment (which is far more interesting).

When I read the links it looks like IBM may have just been sitting and watching this to gobble up the whole data centers when they have been virtualized (VMware, Xen, whatever). It is very much possible that they might pull of the big one with the consolidation move my moving all those (20 vms per box, say) into their own mainframe. After, by 2010, would anyone care if my system runs on Windows or Linux, let alone what Virtualization platform. I don't think that they care today either.

This news article of IBM running 41400 Linux instances on one server:

Ironically, IBM hopes to beat these upstarts at their own game. Thanks to the massive number-crunching power of the S/390 mainframe, it is capable of running hundreds of virtual servers simultaneously.

"Instead of buying 200 Intel boxes, you could run 200 Linux servers on a single mainframe," said Greg Burke, an IBM vice president.

About the size of a big commercial refrigerator, the S/390 is a super fast, crash-proof workhorse used for things like telecom systems, airline ticketing, and big corporate networks, IBM said.

"It's the mother of all servers, without a doubt," said IBM spokesman James Sciales.

The machine, which features up to a dozen 637-MHz processors that between them can execute a mind-boggling 1,614 million instructions per second, in tests ran up to 41,400 separate copies of Linux simultaneously.


Original article + comment

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