Select the product you need help with

You cannot use the Cisco SR-IOV network adapter on a virtual machine in Windows Server 2012

Article ID: 2785638 - View products that this article applies to.

Hotfix Download Available

Expand all | Collapse all

Symptoms

Consider the following scenario:

You have the Cisco Single Root I/O Virtualization (SR-IOV) network adapter installed on a computer that is running Windows Server 2012.
You install the Hyper-V server role on the computer.
You restart or shutdown a virtual machine on the computer.

In this scenario, the Virtual Function (VF) driver that is running on the virtual machine does not receive the Virtual PCI (VPCI) backchannel notification. Therefore, the virtual machine can no longer use the Cisco SR-IOV network adapter.

Back to the top | Give Feedback

Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:

http://support.microsoft.com/contactus/?ws=support

(http://support.microsoft.com/contactus/?ws=support)

Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running Windows Server 2012.

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

Collapse this imageExpand this image

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows Server 2012 file information notes

Important Windows 8 hotfixes and Windows Server 2012 hotfixes are included in the same packages. However, only "Windows 8" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
Collapse this tableExpand this table
Version Product Milestone Service branch
6.2.920 0.20 xxx Windows Server 2012 RTM LDR
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately
(http://bemis/203/_layouts/ArticlePages/DisplayArticlePage.aspx?List=27d133d4%2D10ab%2D4795%2Dbb81%2D092dfe8c7866&ID=373715#Manifests1)
in the "Additional file information for Windows Server 2012" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

For all supported x64-based versions of Windows Server 2012

Collapse this imageExpand this image

Collapse this tableExpand this table

File name	File version	File size	Date	Time	Platform
Vpcivsp.sys	6.2.9200.20573	66,560	01-Dec-2012	04:03	x64

Collapse this imageExpand this image

Back to the top | Give Feedback

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Back to the top | Give Feedback

More information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684

(http://support.microsoft.com/kb/824684/ )

Description of the standard terminology that is used to describe Microsoft software updates

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

Additional file information

Collapse this imageExpand this image

Additional file information for Windows Server 2012

Collapse this imageExpand this image

Additional files for all supported x64-based versions of Windows Server 2012

Collapse this imageExpand this image

Collapse this tableExpand this table

File name	Amd64_wvpcivsp.inf_31bf3856ad364e35_6.2.9200.20573_none_d81ee1d88274706d.manifest
File version	Not applicable
File size	2,118
Date (UTC)	01-Dec-2012
Time (UTC)	06:37
Platform	Not applicable