Hyper-V Best Practices Analyzer

Microsoft released a best practices analyzer for Hyper-V on Windows 2008 R2 only which can be found on the following link :
http://support.microsoft.com/kb/977238/en-us

Hotfix : Windows 2008 R2 + Hyper-V + Intel Nehalem = Blue Screen

If you have Windows 2008 R2 + Hyper-V running on Nehalem CPU(Intel Xeon 5500 or Core-i) and getting blue screen messages with 0x00000101 - CLOCK_WATCHDOG_TIMEOUT stop code then you will definetly need to check the KB below :

http://support.microsoft.com/default.aspx/kb/975530

Before applying the Hotfix to your platform take into account the warning from MS :

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.

Windows 2008 R2 Migration Utilities for Hyper-V

Windows 2008 R2 Migration utilities has been updated with support for Hyper-V. Now it's possible to migrate your Hyper-V setup including VMs,Virtual Switches,VMQ,Chimney Settings etc.. to a Windows 2008 R2 host. The support is from :

Windows 2008 x64 Full Only
Windows 2008 R2 x64 Core or Full Edition to :

Windows 2008 R2 x64 Core or Full Editions. Also from documentation the scenarios that are not supported are  :

• The saved state of a virtual machine under one of the following conditions:
  
  • When moving from Hyper-V in Windows Server 2008 to Hyper-V in Windows Server 2008 R2.
  • When moving between physical computers that have different processor steppings or vendors—for example, migrating from a computer with an Intel processor to a computer with an AMD processor.
• Virtual machine configuration under one of the following conditions:
  
  • When the number of virtual processors configured for the virtual machine is more than the number of logical processors on the destination server.
  • When the memory configured for a virtual machine is greater than the available memory on the destination server.
• Consolidation of physical servers to virtual machines, or consolidation of multiple instances of Hyper-V to one instance.

http://www.microsoft.com/downloads/details.aspx?FamilyID=5c1ec14a-e9d7-46ea-9c6e-73d6bc4219b4

Documentation:

http://technet.microsoft.com/en-us/library/ee849855(WS.10).aspx

Hyper-V Live Migration Network Configuration Guide from Microsoft

Microsoft just released a network configuration guide for Windows 2008 R2 Hyper-V Live Migration feature. It's short but useful article at least for design perspective.

This guide describes how to configure your network to use the live migration feature of Hyper-V™. It provides a detailed list of the networking configuration requirements for optimal performance and reliability, as well as recommendations for scenarios that do not meet these requirements.

 http://technet.microsoft.com/en-us/library/ff428137(WS.10).aspx

Vulnerability in Windows Server 2008 Hyper-V Could Allow Denial of Service - 977894

A new security bulletin by Microsoft has been published today. This DoS vulnerability effects the x64 editions of Windows 2008 and R2 including the Core installations.
http://www.microsoft.com/technet/security/Bulletin/MS10-010.mspx

This security update resolves a privately reported vulnerability in Windows Server 2008 Hyper-V and Windows Server 2008 R2 Hyper-V. The vulnerability could allow denial of service if a malformed sequence of machine instructions is run by an authenticated user in one of the guest virtual machines hosted by the Hyper-V server. An attacker must have valid logon credentials and be able to log on locally into a guest virtual machine to exploit this vulnerability. The vulnerability could not be exploited remotely or by anonymous users.

Hyper-V Memory Overcommitment in new Service Pack for Windows 2008 R2

One of the features in Vmware Infrastructre that was missing in Hyper-V was over-provisioning of memory resources which is also known as memory overcommitment. A leaked screenshot from Softpedia shows that the dynamic memory management features is about to be included in the next Windows 2008 build.

http://news.softpedia.com/news/The-Windows-8-Start-Post-RTM-Windows-7-Build-6-1-7700-0-100122-1900-133746.shtml