Skip to main content

Virtualization: How to cope/co-exist with hyper-disruption as a complementer

Just wrote this up on ITtoolbox.

Really , there is too much happening out there and way too fast. This industry is evolving every few weeks. I saw a couple of authors struggling to keep up the pace with all the advancements.

For instance, lets take VMware here. They first brought out ESX 3.0, a couple of writes/authors or experienced folks in the industry got excited and started writing a book on it. A lot of expertise was put into those books. Loads of scripts, loads of perl stuff and massively cool Linux commands. I've personally never seen a windows admin do a dd so it was really cool to see the guys go crazy with all those commands.

Developers start writing utilities like ESX update utility and loads of other little utility. Vmware goes ahead and releases its 3.5. Oops...plans change as authors have to struggle to keep up with the pace of all the changes that come in and get going with all the new (primarily) GUI utilities such as Update manager etc.

Then boom!!! Here you have the firmwarish version of ESX 3i and suddenly you don't need to get into your Linux consoles and all those custom scripts can go home as that thin, flimsy layer of near-embedded hypervisor is a simple keystroke up/down and all those F1, F2, F11 keys.
Read the rest there.
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

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