Symptoms

Consider the following scenario:

  • You configure a Windows Server 2008 R2-based computer as a failover cluster node.

  • You perform a live migration of a Hyper-V virtual machine from a source node to a destination node.

  • The source node is located on a computer that has an AMD processor that was released earlier than the Bulldozer family of processors. For example, the computer has an AMD Opteron 6100 series processor.

  • The destination node is located on a computer that has an AMD Bulldozer processor. For example, the computer has an AMD Opteron 6200 series processor.

In this scenario, the migration fails, and you receive a message that states that the destination node is incompatible.

Cause

This issue occurs because the AMD 3DNow! technology is deprecated in the AMD Bulldozer family of processors. However, Hyper-V virtual machines incorrectly use the AMD 3DNow! technology when they are in compatibility mode.

Resolution

Hotfix information

After you install this hotfix on the Hyper-V server, update the integration components on the virtual machines. To do this, open the Virtual Machine Connection window in Hyper-V Manager for each virtual machine, and then select the Insert Integration Services Setup Disk option on the Action menu.

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:

http://support.microsoft.com/contactus/?ws=supportNote 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:

976932Information 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:

    Version

    Product

    Milestone

    Service branch

    6.1.760
    1.17xxx

    Windows Server 2008 R2

    SP1

    GDR

    6.1.760
    1.22xxx

    Windows Server 2008 R2

    SP1

    LDR

  • 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 name

File version

File size

Date

Time

Platform

Hvax64.exe

6.1.7601.17944

607,744

30-Aug-2012

15:01

x64

Hvboot.sys

6.1.7601.17944

118,128

30-Aug-2012

18:03

x64

Hvix64.exe

6.1.7601.17944

652,800

30-Aug-2012

15:01

x64

Hvax64.exe

6.1.7601.22103

607,744

30-Aug-2012

15:04

x64

Hvboot.sys

6.1.7601.22103

118,128

30-Aug-2012

18:02

x64

Hvix64.exe

6.1.7601.22103

635,392

30-Aug-2012

15:04

x64


Status

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

More Information

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.

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

824684Description 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 name

Amd64_1811c5b61c54c10189ee1b311a8ef068_31bf3856ad364e35_6.1.7601.17944_none_0a503baaac5aea05.manifest

File version

Not applicable

File size

710

Date (UTC)

30-Aug-2012

Time (UTC)

19:49

Platform

Not applicable

File name

Amd64_d2a740e2186a6b3f646645891dcee9e7_31bf3856ad364e35_6.1.7601.22103_none_0fe8b5e1ddb93b13.manifest

File version

Not applicable

File size

710

Date (UTC)

30-Aug-2012

Time (UTC)

19:49

Platform

Not applicable

File name

Amd64_microsoft-hyper-v-drivers-hypervisor_31bf3856ad364e35_6.1.7601.17944_none_8e56f0a47c3d1a67.manifest

File version

Not applicable

File size

4,163

Date (UTC)

30-Aug-2012

Time (UTC)

18:24

Platform

Not applicable

File name

Amd64_microsoft-hyper-v-drivers-hypervisor_31bf3856ad364e35_6.1.7601.22103_none_8f0aa4f7953b6458.manifest

File version

Not applicable

File size

4,163

Date (UTC)

30-Aug-2012

Time (UTC)

18:24

Platform

Not applicable

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×