Skip to main content

Application Virtualization: Why applications are so crucial

I like reading chuck's blog. I do that primarily because he is focused and addresses issues that we all tend to forget in all the hullo-bullo of virtualization game.

No IT user wants support hassles.

So it's routine to ask any OS vendor, "does application vendor X support your operating environment?". True for all the UNIXes. And true for server/desktop virtualization.

Now, it doesn't matter if the application in question works perfectly; the real question is that -- if there's a support problem -- will the ISV in question will step up and fix the problem?

I think there are two reasons why the answer will usually be a rather unclear "well ...", especially for things like VMware.

First, it costs more for the ISV to support an additional environment, and unless they can see clear incremental revenue (e.g. licenses, maintenance, etc.) it's hard to make an internal case.

Of course, customers beating you over the head helps a bit to move that discussion along.

Second, I think no major ISV really wants interloping vendors below them in the stack. Look at Oracle's repeated efforts to commoditize everything below the database: remember "bare metal" Oracle? Or SAP's preference for Linux? Even Microsoft doesn't have a strong incentive to let others in here.

Ask any ISV of any size a direct question: do you support VMware? -- and you'll get a very contorted answer as a result. It has absolutely nothing to do with technical realities and everything to do with business models and strategic advantage.


Anyways read his insightful post.

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!