Hyper-V Export function consumes all available memory in Windows Server 2008 or in Windows Server 2008 R2

Article translations Article translations
Article ID: 2547551 - View products that this article applies to.
Expand all | Collapse all

On This Page

Symptoms

Consider the following scenario:
  • You install the Hyper-V role on a computer that is running Windows Server 2008 or Windows Server 2008 R2.
  • You use the Export function to export some virtual machines (VMs) to a destination location.
  • The disk I/O transfer rate of the source disk is faster than the disk I/O transfer rate of the destination disk.
In this scenario, the available memory on the computer keeps decreasing. Additionally, the computer stops responding when the available memory is exhausted.

Cause

This issue occurs because the Export function unnecessarily performs buffered copy operations.

The Export function consumes a large amount of cache memory when the following conditions are true:
  • The Export function copies large virtual hard disk (VHD) files.
  • The disk I/O transfer rate of the source disk is faster than the disk I/O transfer rate of the destination disk.

Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that 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=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 one of the following operating systems:
  • Windows Server 2008 Service Pack 2 (SP2)
  • Windows Server 2008 R2
  • Windows Server 2008 R2 Service Pack 1 (SP1)
Additionally, the Hyper-V role must be installed.

For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
968849 How to obtain the latest service pack for Windows Server 2008
For more information about how to obtain a 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 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

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 file information notes
Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" 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 Vista" 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.
    Collapse this tableExpand this table
    VersionProductSR_LevelService branch
    6.0.600 2 . 22xxxWindows Server 2008SP2LDR
  • 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 and for Windows Vista" section. MUM files 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 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Vmms.exe6.0.6002.226673,910,65627-Jun-201113:40x64
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.
    Collapse this tableExpand this table
    VersionProductSR_LevelService branch
    6.1.760 0 . 20xxxWindows Server 2008 R2RTMLDR
    6.1.760 1 . 21xxxWindows Server 2008 R2SP1LDR
  • 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 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 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Vmms.exe6.1.7600.209974,509,18428-Jun-201103:12x64
Vmms.exe6.1.7601.217584,628,48028-Jun-201102:57x64

Status

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

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

Additional files for all supported x64-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameAmd64_b0d10041883deb6f265f1e7953401557_31bf3856ad364e35_6.0.6002.22667_none_94108aa8c1f79259.manifest
File versionNot applicable
File size703
Date (UTC)27-Jun-2011
Time (UTC)17:32
File nameAmd64_microsoft-hyper-v-vstack-vmms_31bf3856ad364e35_6.0.6002.22667_none_94eae3852db85e1f.manifest
File versionNot applicable
File size250,972
Date (UTC)27-Jun-2011
Time (UTC)15:37

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameAmd64_c8b66d0c6592f6f5170c496b176743cf_31bf3856ad364e35_6.1.7600.20997_none_315d1aa4653abb48.manifest
File versionNot applicable
File size703
Date (UTC)28-Jun-2011
Time (UTC)08:51
File nameAmd64_e56870495b2adc7d2d16c8c111d2d870_31bf3856ad364e35_6.1.7601.21758_none_00f265f5d555d4cc.manifest
File versionNot applicable
File size703
Date (UTC)28-Jun-2011
Time (UTC)08:51
File nameAmd64_microsoft-hyper-v-vstack-vmms_31bf3856ad364e35_6.1.7600.20997_none_930bd03891c19c8f.manifest
File versionNot applicable
File size316,002
Date (UTC)28-Jun-2011
Time (UTC)05:55
File nameAmd64_microsoft-hyper-v-vstack-vmms_31bf3856ad364e35_6.1.7601.21758_none_951e6d388ec6b20e.manifest
File versionNot applicable
File size341,338
Date (UTC)28-Jun-2011
Time (UTC)06:57

Properties

Article ID: 2547551 - Last Review: June 21, 2014 - Revision: 4.0
Applies to
  • Windows Server 2008 R2 Standard
  • Windows Server 2008 R2 Enterprise
  • Windows Server 2008 R2 Datacenter
  • Windows Server 2008 Standard
  • Windows Server 2008 Enterprise
  • Windows Server 2008 Datacenter
Keywords: 
kbautohotfix kbqfe kbHotfixServer kbfix kbsurveynew kbexpertiseinter KB2547551

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com