How do I know if a server can be virtualized?

How do I know if a server can be virtualized?

How do I know if a server can be virtualized?

    Requires Free Membership to View

    When you register, my team of editors will also send you the latest expert resources covering all areas of server virtualization, such as platforms, architectures and strategies, server hardware, managing virtual environments, application issues and more.

    Margie Semilof, Editorial Director

    By submitting your registration information to SearchServerVirtualization.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchServerVirtualization.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

While a significant portion of your x86 servers can be virtualized, not every server or application can or should be. If an application requires large amounts of memory, access to a lot of processing power (CPU), or specialized hardware that cannot or should not be managed by the virtual machine software, it should not be virtualized.

Note that at the start of any virtualization project, before performing any physical to virtual migration, you should complete a thorough virtualization assessment, including a performance assessment—captured regularly over weeks, not a snapshot—and a hardware and software inventory. You must know the performance attributes of the server; the existing hardware attributes (third party attachments, host cards, etc); and the support requirements, including any and all third party application support requirements.

Vendors might sometimes want to rush you to the end state without going through the virtualization assessment and planning, arguing that the migration features of the software can "correct" any problems after migration into the virtual space. This, of course, is a mistake--why build any computing environment without a clear picture of the requirements.

This was first published in March 2007