Article ID: 2517374 - Last Review: April 1, 2011 - Revision: 1.0 You cannot start virtual machines on a computer that is running Windows Server 2008 R2 and on which a CPU is installed that supports the AVX feature
On This PageSYMPTOMSConsider the following scenario:
An error occurred while attempting to start the selected virtual machine(s). <virtual machine name> could not initialize <virtual machine name> could not initialize. (Virtual machine ID <virtual machine GUID>) <virtual machine name> Failed to set/change partition property CAUSEThis issue occurs because Windows Server 2008 R2 does not support the AVX feature. RESOLUTIONNote This hotfix package disables the AVX feature on the virtual processors so that the virtual machines can start successfully. You must upgrade to Windows Server 2008 R2 SP1 to support the AVX feature so that the virtual machines can run as expected and to take advantage of the AVX instructions. Hotfix informationA 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=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.PrerequisitesTo apply this hotfix, the computer must be running Windows Server 2008 R2, and the Hyper-V server role must be installed.Registry informationTo use the hotfix in this package, you do not have to make any changes to the registry.Restart requirementYou must restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace a previously released hotfix.File informationThe 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
For all supported x64-based versions of Windows Server 2008 R2Collapse this table
WORKAROUNDWorkaround for Windows Server 2008 R2To work around this issue, you can force compatible CPU flags by setting a WMI property. This property is inaccessible from any user interface (UI). However, this property is documented on the Microsoft Software Developer Network (MSDN) website. You may have to perform this workaround for all virtual machines that are created. The change is persistent after the computer restarts. However, there are two known issues when you perform this workaround. Also, see the following sample Windows PowerShell script.
LimitProcFeatures.ps1:
$VirtualMachines = gwmi -namespace "root\virtualization" Msvm_ComputerSystem
$VMManagementService = Get-WmiObject -Namespace "root\virtualization" -Class Msvm_VirtualSystemManagementService
foreach ($vm in $VirtualMachines)
{
$vmName = $vm.Name
$vmElementName = $vm.ElementName
if(!$vm.Caption.Contains("Hosting Computer System"))
{
Write-Output "Limiting $vmElementName CPU features"
$VMProcessors = (gwmi -namespace "root\virtualization" Msvm_ProcessorSettingData) | where { $_.InstanceID -match "Microsoft:$vmName.*" }
$VMProcessors | foreach { $_.LimitProcessorFeatures = $true}
$retValue = $VMProcessors | foreach {$VMManagementService.ModifyVirtualSystemResources($vm.__PATH, $_.GetText([System.Management.TextFormat]::WmiDtd20) )}
if(!$retValue.ReturnValue)
{
Write-Output "Success";
}
}
}STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. 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. MORE INFORMATIONFor more information about the AVX feature, visit the following Intel website: General information about the AVX feature
(http://software.intel.com/en-us/avx/)
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 Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information. Additional file informationAdditional file information for Windows Server 2008 R2Additional files for all supported x64-based versions of Windows Server 2008 R2Collapse this table
| Other Resources Other Support Sites
CommunityGet Help NowArticle Translations
|
Back to the top
