Responding to "Getting started with Virtualization"

Virtualization is more than just deploying virtual machine software. Working from the big picture usually provides better results.
Written by Dan Kusnetzky, Contributor on

In my usual morning scan, I came across "Getting Started with Virtualization? Read This" which was posted by Rick Vanover. It appears that Rick thinks that virtualization is directly and solely equal to the use of virtual machine software to create virtual servers and virtual desktops. He's asking folks help him understand how to get started.

Rick, a model I published years ago might be use use to you (see Sorting out the different layers of virtualization for more information on the model).

I have found that many vendors see the world through the blinders of  virtual machine software (see Virtual machine software blinders for a longer discussion of the topic) and that focus is really limiting.

Rick, it would be best to seek out what the organization's real goals are before selecting a technological approach.  Here are some thoughts from a previous post that might be helpful.

  • Being able to access applications and data from just about anywhere using just about any networkable device (access virtualization)
  • Being able to run applications or, in fact, full workloads without being concered about potential incompatibilities steming from different versions of operating systems, development tools or application frameworks (application virtualization)
  • Being able to deliver applications to systems when needed without having to deal with time consuming installation processses every single time (application virtualization)
  • Being able to safely and securely access complex organizational networks (access virtualization, network virtualization and security for virtualized environments)
  • Being able to access applications and data even if they were stored in a datacenter halfway around the world (storage virtualization)
  • Being able to process applications faster or support more people’s work than any single reasonably priced system could manage (processing virtualization)
  • Being able to continue operations even if some component failed (processing virtualization)
  • Being able to make a single machine look like many to consolidate or optimize the use of  workloads (processing virtualization)
  • Being able to isolate one workload from another on a single system to worry about incompatibilities or one rogue application breaking into another’s memory or storage space (processing virtualization)
  • Being able to manage many workloads as if they were running on a single computing resource even though they may be spread all over the globe (management for virtualized resource.

I could go on an on, but I think you get the picture.

Editorial standards