Skip to main content

Virtual Iron on "Virtual Monopoly"

All of the ecosystem partners will continue to help further VMware’s success because it is a symbiotic relationship—right now, everyone is making money. But in so doing, there is a big risk that over time, VMware will marginalize most, if not all, of its ecosystem partners.
VMware is in a position to deliver more and more functionality that will increasingly impact the very ecosystem that is complicit in making it successful. Since VMware today is fundamentally an infrastructure company, it will build concentric circles of capability from that point outward. That is why its proprietary file system is so important—it enables VMware to manage and control data. It gives VMware the keys to the kingdom and they know it. Microsoft never quite got this and still doesn’t today. In the meantime, VMware is in a position to create more software that will impact storage, backup and replication.

Many of the ecosystem partners – the server, storage, backup, data protection and operating system vendors – realize this to some degree. But what can they do? They have to play nice. Especially since they are making a boatload of money. So they go about their business and hedge their bets by supporting Microsoft and Citrix to create a balance of power. Microsoft gets a thumbs up because it’s– well – Microsoft. It doesn’t matter if its product isn’t available and will have major limitations for one, two, or maybe even three years. Citrix is invited to the party because it bought XenSource and even though it doesn’t have a fully functional product, it gets a pass because it is a big company and everyone assumes that it will get there. VMware is fully supportive of this, telling the world that it wants healthy competition. But everyone knows—even though they won’t say it out loud—that VMware wins in this scenario.


More here...

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...