Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

AVX instructions do not work in a virtual machine on a Windows Server 2008 R2-based computer that has an AMD CPU which supports the AVX feature


View products that this article applies to.

Symptoms

Consider the following scenario:
  • An AMD CPU that supports the Advanced Vector Extensions (AVX) feature is installed in a computer that is running Windows Server 2008 R2.

    Note AMD introduces support for the AVX feature in Bulldozer-based multicore processors.
  • You install the Hyper-V server role on the computer.
  • You create a virtual machine on the computer, and then you start the virtual machine.
In this scenario, AVX instructions do not work as expected on the virtual machine.

↑ Back to the top


Cause

This issue occurs because the CPUID maximum function limit is not updated to reflect the support for the AVX feature on AMD processors.

↑ Back to the top


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 the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

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, contact 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: 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 2008 R2 Service Pack 1 (SP1).

For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To apply this hotfix, 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

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 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" 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, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
    VersionProductMilestoneService branch
    6.1.760
    1.17xxx
    Windows Server 2008 R2SP1GDR
    6.1.760
    1.21xxx
    Windows Server 2008 R2SP1LDR
  • GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. 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 2008 R2
File nameFile versionFile sizeDateTime
Hvax64.exe6.1.7601.17876610,81629-Jun-201204:00
Hvboot.sys6.1.7601.17876118,12829-Jun-201207:36
Hvix64.exe6.1.7601.17876652,28829-Jun-201204:00
Hvax64.exe6.1.7601.22034607,23229-Jun-201203:57
Hvboot.sys6.1.7601.22034118,12829-Jun-201207:36
Hvix64.exe6.1.7601.22034635,39229-Jun-201203:57

↑ Back to the top


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


More Information

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

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

Additional file information

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
File nameAmd64_1bd5b472e689c267836aa8c6e9e1126e_31bf3856ad364e35_6.1.7601.17876_none_8941729a232bef2a.manifest
File versionNot applicable
File size710
Date (UTC)29-Jun-2012
Time (UTC)16:33
File nameAmd64_283ed9894180910cde327c18e5e5c4a0_31bf3856ad364e35_6.1.7601.22034_none_bd200a603bccb6ee.manifest
File versionNot applicable
File size710
Date (UTC)29-Jun-2012
Time (UTC)16:33
File nameAmd64_microsoft-hyper-v-drivers-hypervisor_31bf3856ad364e35_6.1.7601.17876_none_8e387f8e7c53a3c1.manifest
File versionNot applicable
File size4,163
Date (UTC)29-Jun-2012
Time (UTC)10:35
File nameAmd64_microsoft-hyper-v-drivers-hypervisor_31bf3856ad364e35_6.1.7601.22034_none_8eeb33979552d45b.manifest
File versionNot applicable
File size4,163
Date (UTC)29-Jun-2012
Time (UTC)10:38

↑ Back to the top


Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseadvanced

↑ Back to the top

Article Info
Article ID : 2712156
Revision : 1
Created on : 1/7/2017
Published on : 10/12/2012
Exists online : False
Views : 162