Skip to main content

Ed Walsh, CEO Virtual Iron: "Don't get into the vendor lock"

Funny, I speak to many IT folks in the past and have heard the same news around the IT manager circles. People are scared to get into to complex locks while the road to freedom and the flight to the Clouds is the shining light at the end of the tunnel. The "transitional vehicle" that virtualization is today, should not be a place where you want to get you ass glued too. But actually the decoupling of the app stack from your hardware layer does make it easier to make that move to the "Query 3.0" architecture which the clouds will try to help you with eventually.

The battle to move on from one vehicle to another is pretty much ,rather primordial, the same. Today we are getting people excited because they spent all their time discussing and talking and now they are willing to budge. Same challenges will be there tomorrow...this is also called the fear of Change.

Anyways, I am sure Ed didn't get too conceptual or philosophical with all this, he simply said:

"Storage design decisions are critical. Don't build out separate islands," he advised, in a tacit swipe at VMware. VMware's popular VMotion product can move running virtual machines around, provided they are using a shared storage file format from VMware. Virtual Iron offers LiveMigration in place of VMotion.

The Lowell, Mass., firm has previous received $8 million in 2003, $12 million in 2004, $11.5 million in 2005, and $13.5 million in July 2007, according to company spokesmen. The same backers have been involved in the previous rounds. Intel is interested in speeding up adoption of virtualization via investment through its venture capital arm because virtualized servers in many cases thrive with the latest versions of its chips. Hooks to the hypervisor have been built into the chips instruction set to speed some forms of virtualization processing requirements.

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

OS Virtualization comparison: Parallels' Virtuozzo vs the rest

Virtuozzo's main differentiators versus hypervisors center on overhead, virtualization flexibility, administration and cost. Virtuozzo requires significantly less overhead than hypervisor solutions, generally in the range of 1% to 5% compared with 7% to 25% for most hypervisors, leaving more of the system available to run user workloads. Customers can also virtualize a wider range of applications using Virtuozzo, including transactional databases, which often suffer from performance problems when used with hypervisors. On the administration side, customers need to manage, maintain and secure just a single OS instance, while the hypervisor model requires customers to manage many OS instances. Of course, the hypervisor vendors have worked hard to automate much of this process, but it still requires more effort to manage and maintain multiple operating systems than a single instance. Finally, OS virtualization with Virtuozzo has a lower list price than the leading hypervisor for comme...