Notes from VMM 2008 R2 P2V conversion

Posted: 19th September 2011 by Seth Killey in Virtualization

This past weekend I used Microsoft’s Virtual Machine Manager 2008 R2 to perform a physical to virtual conversion of a production Windows 2008 server.  I encountered a few stumbling blocks and so I figured I’d document how I overcame them while it’s still fresh in my mind.

  • The first attempt I made at performing a P2V failed with the following error below.  After doing some research I decided to temporarily disable all anti-virus real-time protection on the host server.  I use AVG 2011, but each AV program is a little different so consult with your AV documentation.

Error (12700)
VMM cannot complete the Hyper-V operation on the <servername> server because of the error: ‘<servername>’ failed to add device ‘Microsoft Synthetic Ethernet Port’. (Virtual machine ID 1EF318A1-929E-4B70-AA66-2E2FF87A26B0)

The Virtual Machines configuration 1EF318A1-929E-4B70-AA66-2E2FF87A26B0 at ‘\\?\Volume{22af413c-1122-4d78-96e8-75b1aea68d39}\<servername>’ is no longer accessible: The requested operation cannot be performed on a file with a user-mapped section open. (0x800704C8)
(Unknown error (0x8000))

Recommended Action
Resolve the issue in Hyper-V and then try the operation again.

  • Once my anti-virus real-time protection was disabled I attempted to restart my failed job.  However, I got the following error below.  I followed this technet article and performed each of the steps listed, each time attempting to restart my failed job with the same error.  Ultimately, I decided to cancel the failed job and start fresh with AVG disabled which allowed me to complete the wizard successfully.

Error (2915)
The WS-Management service cannot process the request. Object not found on the <servername> server.

Recommended Action
Ensure that the agent is installed and running. If the error persists, reboot <servername> and then try the operation again.

  • A couple items related to cleanup after the wizard completes
    • The Windows licensing on the newly created VM will likely need to be re-activated.
    • On my new VM, I noticed one of my drives was really low on disk space.  I noticed that at some point during the conversion process it must have created a pagefile on my OS drive, whereas on the production, physical server I had moved the pagefile to a different volume.  I was able to unhide hidden folders and unhide operating system files to locate the large pagefile and safely delete to free up space.  Obviously, make sure the pagefile is no longer in use before deleting
    • While I’m on the topic of pagefiles, for some reason on one server it allows me to have the pagefile on a virtual SCSI controller, yet on a different VM it does not, forcing me to put the pagefile on my system drive which uses IDE.  This KB article explains why it shouldn’t work  Just weird that it does work on one VM and not the other.
    • I’m not sure if I missed a step in the wizard, but if you plan on using the hardware from the recently virtualized server, make sure you edit the network card settings in Hyper-V so the VM uses a dynamic MAC address.  Otherwise, if you format and bring back the old hardware there will be a duplicate MAC address on your network because the VM will be using the same static MAC address
    • If you encounter an error with the wizard as described below, you may have issues with removing the failed VM from your Hyper-V host.  I found this excellent post which resolved the issue for me
    • Lastly, this is more MS Exchange specific, but this VM was my hub transport server and after pulling up the newly created VM, outgoing mail was failing due to MX / DNS lookup failures.  What I determined based on the event log is that the Hub Transport references the old physical NIC.  I was able to refresh this setting with the newly created, generic virtual NIC by going into my MS Exchange Administrator Console, clicking on Server Configuration –> Hub Transport –> select Properties on the server object –> Go to the External DNS Lookups tab –> select the virtual NIC from the drop down menu, click apply, and then restart the Hub Transport Service.  I did likewise for Internal DNS Lookups for safe measure