Home > Hyper-V, Hyper-V R2, SCVMM, SCVMM R2, Tips&Tricks > How to fix slow offline P2V times in VMM b/c of duplex switches

How to fix slow offline P2V times in VMM b/c of duplex switches

Source

Michael Michael has shared some content that is very useful about troubleshooting offline P2V.

if you are experiencing a slow offline P2V time due to a network that has 100mb full duplex enabled on the switch end, here is the process you can follow to make the data transfer a lot faster. This process will modify the WIM image used for P2V and modify the type of networking drivers being used, The entire process is reversible as long as you copy back your backup WIM image from step #4 and replace the changed one with the backed up one.

1.       Enable tracing on the source computer during an offline P2V. (create a file named scvmm_enable_winpe_tracing.txt and save it to the root of the source computer’s boot volume before you start the P2V). This file does not need to contain any data or information. A trace file named scvmm_winpe.etl will be created and saved on the source computer.

2.       Start the P2V and the stop it after it starts to copy the hard disk.

3.       Log back onto the source machine and find what Network driver WinPE loads during the P2V (There should be a text file on the system drive that WinPE has created)

4.       Copy the boot.wim file from the VMMData directory on the VMM Server to a new directory (Make a copy just in case anything goes wrong!)

5.       Using imagex from the Windows WAIK (Located under Program Files\Windows AIK\Tools\amd64) , mount the boot.wim file as ReadWrite(Example: imagex /mountrw d:\temp\boot.wim 1 d:\temp\Mount)

6.       Open the directory where the image was mounted to and navigate to the WinPE driver repository (Windows\System32\DriverStore\FileRepository)

7.       Open the folder that contains the driver, then the inf file.

8.       Search for “Duplex” > Find each section of the inf that references this key and modify the default to what you want.

9.       Save the file and then commit the changes back to the Wim file (Example: imagex /unmount /commit c:\mounted_images)

10.   Copy the Boot.wim file and replace the one under the VMMData directory in SCVMM.

11.   Start the P2V and watch it fly J

This blog post is courtesy of Andrew Auret.

Advertisements
  1. ankiefran
    September 15, 2010 at 10:41 am

    Alternatively if you are able to change the port on the switch to auto i found this worked very well and was much quicker to do. I realise a lot of people don’t have that control over their network ports however
    The reason for the slow transfer in my case was that the network port was forced to 100mb/full and the PE boot wanted to auto negotiate. Auto negotiation only works well if both server and switch are configured to auto. My server and switch were configured to 100mb full but PE couldn’t negotiate properly with the switch and so set itself to half duplex . File transfer before i set the switch to auto was 24 hours for a 6gb drive. Once i set the switch to auto it took 40 minutes

  2. Mohamed Fawzi
    September 15, 2010 at 2:07 pm

    Thanks a lot for these information

  1. March 12, 2010 at 4:23 am

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: