Everyday Virtualization

Blog archive

P2V Pain Points

Physical-to-virtual (P2V) conversion tools are very good nowadays. Beyond the tools, the support network and mechanisms are very well defined. If you are having a problem converting a system, chances are someone else has had the same problem.

This is relevant to me right now for two reasons. The first is that I converted a machine that I never thought could be converted. I did kind of a virtual happy dance in my Twitter feed. Twitter is a good source of all kinds of information fory my virtualization efforts and life, as well as the other virtualization experts I follow. The second reason that conversions are front burner for me now is that I am starting preparations for the TechMentor conference in Orlando, where I will present on advanced conversions for virtualization.

As part of the decision tree that goes with a P2V conversion, the most important question is “Should this system be converted?” Inevitably the answer is “It depends.” Unfortunately, there is no steadfast guidance for all organizations on when a P2V conversion should be passed up for non-technical reasons. Factors such as older operating systems, unstable software configuration, length of continued use, licensing, storage costs and more can make a P2V conversion a bad idea in some situations.

The goal is to avoid trouble down the road, and these (mostly) non-technical issues can cause issues downstream. What are some of the non-technical issues that can cause P2V pain for your environments? Send me a note or drop a comment below.

Posted by Rick Vanover on 04/14/2009 at 12:47 PM


Subscribe on YouTube