Fix for "Sandy Bridge" Processors Issue on Windows Server 2008 R2 Hyper-V and Hyper-V Server 2008 R2

Intel has recently released their new "Sandy Bridge" processors which is the second generation of the Core i3/i5/i7 processors. Microsoft has confirmed a issue involving virtual machines failing to start on servers powered by Intel Sandy Bridge CPUs.According to the Redmond company, virtual machines running on servers with either Windows Server 2008 R2 Hyper-V or […]

Intel has recently released their new "Sandy Bridge" processors which is the second generation of the Core i3/i5/i7 processors. Microsoft has confirmed a issue involving virtual machines failing to start on servers powered by Intel Sandy Bridge CPUs.

According to the Redmond company, virtual machines running on servers with either Windows Server 2008 R2 Hyper-V or Microsoft Hyper-V Server 2008 R2 and the new Sandy Bridge processors can be impacted by this issue. It appears that the glitch is accompanied by the following error message "<VM Name> could not initialize" being logged and displayed in Event Viewer.

At this point in time there are only following two solutions that customers can turn to in order to resolve the problem described above:

  • Option 1: Upgrade Windows Server 2008 R2 and Microsoft Hyper-V Server 2008 R2 with Service Pack 1 which properly supports the new Sandy Bridge Processors. After installing Windows Server 2008 R2 SP1, it adds support for the AVX instructions in the parent partition and within the virtual machine for guest operating systems.
  • Option 2: Apply this hotfix to Windows Server 2008 R2. After installing this hotfix, it adds support for the AVX instruction in the parent partition, but does NOT present AVX instructions within the virtual machine for guest operating systems.

[Via: Virtualisering DK]