Skip to main content

Open standard Virtualization?



Pete Loshlin argues that the proprietary aspect of Virtualization which forces end users to use Servers/HW that are supported by top virtualization vendors like VMware, Microsoft, VirtualIron, to name a few, will eventually be washed away with Open Standards. I do too believe with open standards and eventually (I've been saying this about everything) a lot of things that we use to trade (meaning busy and sell) will be just free!

Anyways, this is what he says about the future


What does the future hold? Virtualization will gain importance, particularly as hardware vendors continue to rollout new products that support so-called "bare metal" virtualization, under which the hardware platforms perform some of the functions currently offered by virtualization software. Because it changes the way server and OS software is installed, Microsoft will continue to view virtualization as an important opportunity. Ultimately, they will either attempt to dominate the market by purchasing a company such as VMware; or if consumers are swayed to a more open standard such as that offered by Xen, Microsoft would, reluctantly, begin to support the standard.

Ultimately, the trend over time will be for businesses to move their business intelligence and other large and complex applications away from proprietary hardware and software that scales poorly, that demands significant staffing to maintain and that tends to lock businesses into specific vendors. Virtualization will permit businesses to treat their computing resources as fungible assets rather than as rapidly depreciating and underutilized cost centers.


Interesting. Read on...
Labels:

Comments

Post a Comment

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
Post a Comment
Read more

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
Post a Comment
Read more