Skip to main content

Application Virtualization: Developers need to participate in this convegence!

When an application that hasn't been certified to run on virtual servers encounters technical issues that prevent it from working properly, a user can be left in a bind if none of the involved parties -- the virtualization or operating system vendors, or the ISV -- is willing to step up and fix the problem.

Such situations can result in "a lot of finger-pointing, which is what the user really wants to get around," said Christopher Voce, an analyst at Forrester Research Inc.

The support issue hasn't come to the fore yet because early virtualization adopters have mostly been large enterprises with sufficient clout to demand personalized help from reluctant software vendors, said IDC analyst Michelle Bailey. "The basic message is, 'Either support me or I'll find some other ISV that will -- or maybe I'll go open-source,'" Bailey said.

But she added that as virtualization software trickles down to smaller and less cutting-edge companies, those users "will be more conservative in their approach and will be looking for compliance [from vendors] upfront."


Link

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!