70-659 Exam Prep Part 13

Performing physical-to-virtual (P2V) and virtual-to-virtual (V2V) migrations

Virtual Machine Manager (VMM) has an intelligent placement feature that allows the VMM admin to place VMs on host servers to best suit the needs of the work load or performance of the VM in question.

Ideal placement is suggested based on a star rating for the hosts. There are some scenarios -where intelligent placement comes into play. This includes: New VM (from a template, from a disk, or from a VM), New P2V, New V2V, Migrate VM (quick, Live, storage, or network-based migration), or deploying a VM from the library. There are also some factors that impact intelligent placement:

VM settings: Processor Count, Memory Amount, Virtual Disks on IDE Controller, High Availability, Virtual Disk size

VMM can also reserve host settings which can impact intelligent placement. Those settings are: CPU percentage, memory (in MB), disk space (in MB), maximum disk I/O per second, and network capacity percentage.

If the standard star rating doesn’t suit your needs you can customize the rating system. There are a few ways VMM allows for customization of the rating system:

Resource maximization (preferred hosts with the most resources or hosts that meet the VMs’ needs) Load balancing (spreading VMs over as many hosts as possible to prevent overwhelming any one host).

A second way is to customize the main VM resources; CPU, memory, disk I/O, and network utilization. A third way is to specify the VM load for the CPU, disk or network.

You may have some servers that you need to convert to VMs. Could it be that where they are, they are being under-utilized? There are a few things that can be done in this instance. This is where Physical to Virtual (P2V) and Virtual to Virtual (V2V) migrations come in.

P2V is the process that VMM uses to convert the contents of a physical server into virtual machine. There are two methods of doing P2V migrations; offline and online.

V2V is the process of converting VMware ESX VM files to VHD files. You can do this either online or offline too.

Performing online /offline P2V

Virtual Machine Manager (VMM) has a wizard that takes you through the process of doing a P2V migration. You will need to supply the name of the physical server you want to migrate, an administrative account, password and domain name. Next you will need to specify the VM name to which the physical server will be copied to, who the owner is, and a description. After all this is done, VMM will install a P2V agent on the physical server and begin the P2V process. The following table outlines what OSes are supported:



P2V mode

Windows server 2000 Server SP4



Windows XP SP2+



Windows XP SP2+



Windows Server 2003 SP2



Windows Vista SP1



Windows Server 2008



Windows 7



Windows Server 2008 R2



Source: Mastering Virtual Machine Manager 2008 R2, Sybex (Note: parts of this list may be out of date)

If an OS is not in the list, it is not supported.

For offline P2V, the process is similar, however, in the offline P2V wizard you will need to specify IP information. The offline process will create a WinPE image. VMM will deploy the image to the specified system, alter the boot order and restart the server. WinPE will start up and begin the copying process to the VMM server.

Performing online /offline V2V migrations

VMM has a V2V wizard that can convert VMware files to VHDs. First VMM must control a VMware environment. The VMware Tools must be uninstalled and the VM must be turned off. Next, run the VMM V2V wizard and supply all requested information and settings for the new VM. Note that V2V needs the VMware file type VMDK in a support format. There is no online method for V2V.

Performing import/export migration

If you find yourself needing to move VMs between servers, aside from migrations, you can export and import VMs.

Exporting a VM can be done through Hyper-V Manager. When you export a VM you get the following dialogue box. All you need to do is to specify where the VM will be saved. A copy will be made. Note also that the VM must be turned off before exporting.


When importing a VM you will be presented with the following dialogue box:


Specify where the VM is located and the import settings.

Move or restore the virtual machine (use the existing unique ID): This option imports the original VM retaining its original ID.

Copy the virtual machine (create a new unique ID): This option imports the VM assigning it a new ID.

Duplicate all files so the same Virtual machine can be imported again: This option will create a new VM in the same location as the original.

Comments are closed.