Skip to main content

Virtualization Market: A Real-Time Market Analysis

Watching folks panic and start picking up glass-balls and attempting to predict the future made me worry a bit. I got drawn to it and indeed fell prey to the trap. So I got myself thinking and wrote up a little piece of what we ought to expect from this evolving market.

Real-Time Market Analysis

We are at the brink of a cylindrical upstaging. VMware is more challenged than any other party we have to mention today. KVM is the least worrisome of the rest. Microsoft's Hyper-V has its own trajectory and will soon define and refine its own strategy as it goes on embedding (maybe they'll just call it embedding and still do the old fashioned hulky-bulky way) its "virtualization technology" into all their core-applications (where they draw a revenue of $12Bn yearly, more or less).

Citrix's purchase of Xen is indeed still an edible, digestible and maybe at some time in the future a launchpad (I am not saying disposable) to its future directions. Could that be a possible acquisition path or could it mean that Citrix would rise until we really would start believing when the products get recognition and start feeding the market or vice versa? Well its own market is still healthy and is growing smartly. When Microsoft came out with its Terminal Server we all thought that it'd be a killer, somehow that didn't happen. We saw an excellent complementer-complementee (not a word, I know) develop the last couple of years.

VMware has to learn to cope with challenges, not the ones that it expects to come at dizzying high velocities but the ones that will gradually spread around it. That is where my "Funnel Strategy and Puddle Convergence Framework" comes in handy. VMware has got to learn to get its ever-expanding and increasingly isolation-prone product suite and strategy puddle to find its way out through a funnel towards the industry. This is definitely not an easy task, it was done to it with EMC's acquisition , now it has to do it to itself!I was inspired about it when Citrix went for XenSource. Citrix and XenSource both have a great opportunity to do the Funnelized Covergence and finalize its direction. Most of my analyst buddies across the world saw it as a significant development, note that we didn't see it as a "Finally we have someone who'll nail VMware down!". Some folks may feel the same frustration when they will see Microsoft approach gradually by starting its low-level entry at the "markets where VMware is not active yet" as the Microsoft executive put it rather humbly.

So will VMware meet the fate of PrairieTek? We sure hope not, we don't want a firm that has done so much for the industry to go down that poorly. It hurt me tremendously when I heard (months back) about Qlusters's "destructive strategic intent" and knew that eventually it would have to close down its shop. VMware may not be on a destructive path but it surely has to cover a lot of ground in terms of maturity, business acumen, industrialization and market relevance. Market relevance must not be confused with market presence. Many firms have had momentary success with such market presence. Market relevance does not necessarily has to mean that the products are excellent, it only means that a firm X has average products and excellent practices. VMware still has to build its practice around its products but again its still a pretty young company and has a future, just like any other firm such as Citrix, Microsoft, IBM etc.

KVM has been spoken about at large in the rumor circles and may of my good friends have been whispering in my ears that IBM, HP are all hatching a secret plan to dump Xen. Well they are building an offering in all flavors for all flavors. Last I heard HP was doing Parallels (and this is today’s news, BTW). KVM is more of a flavorism thing than a favorism thing. KVM is yet another color to your virtual cloud-set. That’s just about it. It may get popular, like I said, it is beginning to get recognition and it can only grow up until we find something else and fall in love yet again!

And that is what I call a cylindrical upstaging and bloggers are getting carried away once in a while ;-)

Disclaimer: I hold nothing against Brian or any propensity to what Simon says or does. Brian is a nice fella and although I haven't spoken to him, I'm sure he's an ok dude. Simon is a nice fella and I’ve spoken to him and is an ok dude too. So peace J

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