If you are experiencing failures when you perform P2V conversions using VMM you should create on the source computers boot drive a file called scvmm_enable_winpe_tracing.txt. The source computer is the computer that you are trying to convert to a virtual machine. Once done you will need to run the P2V conversion again. During the new P2V conversion VMM will create a new file called: scvmm_winpe.etl.
This file should have all the information needed to troubleshoot a failed P2V conversion.
The default location of the folder can be found here:
C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\Patch Import
You will most like need to use this if you are getting errors with P2V or V2V migrations and it’s complaining about drivers.
Here’s an example of people having issues an needing to place files in this location. The command you need to use is the Power Shell “Add-Patch” command.
Wanting to learn a bit more about HYPERV. Take a look at the HyperV and VMM categories on the right hand side.
To change the MAC pool range in HyperV manager open HyperV Manager. Select the server and right click it. Select “Virtual Network Manager”
Under Global Network Settings select MAC Address Range
To change the MAC pool range in System Centre Virtual Machine Manager (scvmm) open up VMM. Once open click on “Administration”.
Double click “Global Static MAC address Range”.
Enter the values you would like to enter.
The difference between HyperV Manager’s approach and SCVMM to Mac addresses is that HyperV Manager you can only specify the MAC address range per server. SCVMM you can specify the MAC range for all the VMMs created on any hosts that are being controlled through SCVMM.
Are you trying to use Virtual Machine Manager (VMM) and getting the VMM 609 error?
You aren’t alone. I figured out this morning it is related to the integration components and that they are not at the same level as the server. Months ago I create a new VM. After creating it I sys-prepped my machine and used the sys-prepped drive as part of my templates in the VMM library. Since creating the template my server got updated and so did the integration components. Because of this, when I went to go use the template I got heart beat errors because the VM and Host are not at the same level.
Lesson learned? Well, make sure that you always have the same integration components installed. Want to learn from my Hyper-V mishaps? Check out the Virtual Machine Manager & Hyper-V section of my blog.
Are you getting the error: “The VMM server domain functional level is . VMM requires a minimum domain functional level of 2.”?
You might be surprised that the Virtual Machine Manager Configuration Analyzer will spit this message out if you aren’t logged in as a domain admin when you run the tool!
Log off and log back on as a domain admin and you won’t have to worry about this issue anymore!
Hope this helps someone else.