Symptoms
Windows server is unable to load the Virtual Fibre Channel driver for Hyper-V NPIVCustomer has recently converted a Windows 2008 R2 SP1 server to a virtual machine. In Hyper-V Manager on the Hyper-V Server running 2012 R2, when he "Add Hardware" and "Fibre Channel Adapter" it fails to creates the virtual HBAs for the virtual machine. It fails to load the driver on the VM Windows 2008 R2 server.From the EMCReports we see SETUPAPI.DEV.LOG dvi: vmbus\{2f9bcc4a-0069-4af3-b76b-6fd0be528cda} cpy: Policy is set to make all digital signatures equal. dvi: Enumerating INFs from path list 'C:\Windows\inf' inf: Searched 0 potential matches in published INF directory inf: Searched 36 INFs in directory: 'C:\Windows\inf' dvi: {Build Driver List - exit(0x00000000)} 17:52:40.684 ndv: Selecting best match from Driver Store (including Device Path)... dvi: {DIF_SELECTBESTCOMPATDRV} 17:52:40.684 dvi: No class installer for 'Unknown driver software package' dvi: Default installer: Enter 17:52:40.684 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. dvi: {DIF_SELECTBESTCOMPATDRV - exit(0xe0000228)} 17:52:40.684 ndv: {Core Device Install} 17:52:40.684! ndv: Installing NULL driver! dvi: Set selected driver complete. dvi: {DIF_ALLOW_INSTALL} 17:52:40.684 dvi: No class installer for 'Unknown driver software package'
Cause
Integration Services was not installed on the virtual Machine.For Windows 2008 R2 SP1 and below, you must install integration services after the server has been migrated to a VM. Windows 2012 and above have Integration Services Built-in.
Resolution
Install the integration services after you set up the operating system in the virtual machine.See Microsoft Integration Services for Hyper-V for more information.https://technet.microsoft.com/en-us/library/dn798297(v=ws.11).aspx
