This guide demonstrates how to virtualize a physical machine running Windows. It requires a VMM server managing at least one Hyper-V host available for placement. The physical machine must be connected to the same network as the Hyper-V host and the VMM server for successful conversion. Additionally, local or domain administrative credentials are required. The process is initiated from the VMM console and is completed using the wizard. Powershell script included.
For VMM to be useful, you need to add servers to a host group for management. The easiest method, involves adding servers in a trusted domain using a ‘Run As’ account different from the account you use to log in to VMM. You can also add servers in untrusted domains or on a perimeter network, although this is slightly more involved. You can even provision a bare-metal host through a baseboard management controller. This guide will outline the steps of adding a host in the same domain, on the same network.
Once you have gone through the lengthy and specific requirements to install and get VMM running (See http://technet.microsoft.com/en-us/library/gg610592.aspx for all the requirements), added your physical servers to a host group for management, and configured networking ‘fabric’, you can use VMM to perform live migration between your servers running the same version of Hyper-V.
Note that starting in Hyper-V 3.0 VMM is no longer needed to perform live migration; they can be initiated directly in Hyper-V manager.
This guide assumes a pre-configured VMM, server, and network infrastructure (see the technet article for more information).
After previously having to use System Center Virtual Machine Manager for live migration of VMs, it is now possible to set up Hyper-V 3.0 for live migration directly through the Hyper-V manager console.