Skip to main content

Virtualization Real-Time Analyst Prediction Series

I've begun writing a series on Virtualization predictions and suddenly I realized that this will go on for the whole year!

Why am I writing it on CEB (NYSE::EXBD) blog at ITtoolbox and not on my blog?

Answer is simple. Obviously I want you to come to my blog but I want you to come to where the community is. I am NOT the community, I am a mere mortal and maybe a one-man firehose from this end. So while I am shooting myself in the leg by talking about it within the community and not on my "Legacy Blogging Style". Anyways back to the community. I will be covering:

  1. Server virtualization trends
  2. Vendor strategies and evolving eco-system
  3. Solutions provider's evolution strategy (For instance what should our solution suite should look like: Virtualization top down, bottoms-up complemented with security, VMLM, ITSM, DRP, etc all baked-in). Here they should also develop these models with Virtualization vendors.
  4. Customer-friendly solution that develop models for developing "entry and exit" strategy. Note: Here with the maturity and adoption of other hypervisors gets pervasive, customers must go virtual.
More will come here, keep watching this space.

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