asked on

Offline VMM P2V issues.

Hello,

We are having issues with our P2V offline conversion. We get to the stage whereby the source computer is restarted, goes into WinPE, then fails with a 3133 error.

http://social.technet.microsoft.com/wiki/contents/articles/439.vmm-troubleshooting-p2v-conversion-issues.aspx

There is the information on that specific error. It pertains to a loss of connection between the host and source after WinPE is loaded on the source. The error mainly states that is a network driver issue.

So, I then read this page;

http://support.microsoft.com/kb/970921

On that page it suggest reading the log files during a WinPE boot. As this is a live server, we cannot touch this until the weekend, but we still had a look at the logs to check when the P2V failed.

The logs are attached, could we have some assistance in deciphering them. To view the full log, please see attached!

This is the first failure - it appears to be a VGA driver? Which is strange.
The source machine is 2008R2 - the host machine is 2008R2 with Hyper-v and VMM2008. Assuming this is a VGA driver issue, we will add the correct driver to the folder "Driver import" on the host machine.

The second failure, is a bit harder to figure out. Is this a chipset driver issue?

>>>  [DIF_SELECTBESTCOMPATDRV - PCI\VEN_102B&DEV_0522&SUBSYS_01018086&REV_02\4&1F820512&0&00E4]
>>>  Section start 2013/07/06 09:36:27.828
      cmd: winpeshl.exe
     dvi: No class installer for 'Video Controller (VGA Compatible)'
     dvi: No CoInstallers found
     dvi: Default installer: Enter 09:36:27.828
     dvi:      {Select Best Driver}
!    dvi:           Selecting driver failed(0xe0000228)
     dvi:      {Select Best Driver - exit(0xe0000228)}
!    dvi: Default installer: failed!
!    dvi: Error 0xe0000228: There are no compatible drivers for this device.
<<<  Section end 2013/07/06 09:36:27.828
<<<  [Exit status: FAILURE(0xe0000228)]

>>>  [DIF_SELECTBESTCOMPATDRV - PCI\VEN_8086&DEV_3423&SUBSYS_00DC0086&REV_22\3&11583659&0&A2]
>>>  Section start 2013/07/06 09:36:28.358
      cmd: winpeshl.exe
     dvi: No class installer for 'System Interrupt Controller'
     dvi: No CoInstallers found
     dvi: Default installer: Enter 09:36:28.358
     dvi:      {Select Best Driver}
!    dvi:           Selecting driver failed(0xe0000228)
     dvi:      {Select Best Driver - exit(0xe0000228)}
!    dvi: Default installer: failed!
!    dvi: Error 0xe0000228: There are no compatible drivers for this device.
<<<  Section end 2013/07/06 09:36:28.358
<<<  [Exit status: FAILURE(0xe0000228)]

Open in new window

Thanks for any and all help.
scvmm-winpe-setupapi.log

Aaron Tomosky

http://vendev.org/pci/ven/8086/dev/3423/

Odd to have an intel chipset driver missing..

SpencerKarnovski

ASKER

Am I being dumb here, when you say "intel chipset driver missing" is this driver missing from the source computer - e.g, the server that is getting visualised (offline), or does this driver need to be placed in the driver import folder on the host?

The process is not clear to me.

When the host server (the one with VMM on it), shuts down the source computer, and boots that into WinPE, then comes up with the error in the log above, I'm right in assuming that its the actual source server that is missing the driver, and not the host server? So when drivers are missing, you add them to the driver import folder.

ASKER CERTIFIED SOLUTION

Aaron Tomosky

membership

Create a free account to see this answer

Signing up is free and takes 30 seconds. No credit card required.

See answer