Here are a few good links documenting the upgrade of Hyper-V R2 clusters to SP1 including a list of updates and hotfixes related to this combination. Please also read the warning at the end!
- Upgrading a Hyper-V R2 Cluster to Windows Server 2008 R2 SP1: http://workinghardinit.wordpress.com/2011/02/17/upgrading-a-hyper-v-r2-cluster-to-windows-2008-r2-sp1/
- Hyper-V Failover Cluster Step-by-Step Guide Rolling Upgrade SP1:
- Hyper-V Dynamic Memory Configuration Guide:
- Make sure you run Cluster Validation after the upgrade of all cluster nodes has finished: http://technet.microsoft.com/en-us/library/cc726064.aspx
- FAQ Dynamic Memory and RemoteFX (Windows Server 2008 R2 SP1): http://kristiannese.blogspot.com/2011/02/faq-dynamic-memory-and-remotefx-windows.html
- Windows 2008 R2 SP1 general availability and what it means for Exchange: http://blogs.technet.com/b/exchange/archive/2011/02/11/3411983.aspx
- Support policy for Microsoft SQL Server products that are running in a hardware virtualization environment:
- Here is the link to SP1 itself:
The following spreadsheet filters updates and hotfixes for Hyper-V and Cluster:
WARNING AND DISCLAIMER:
I would like to stress that upgrading to SP1 is not something that should be taken lightly. Make sure your backups are secure and you know you can restore those backups.
So far our test upgrades have been fairly easy and without any problems. Cluster Validation completed 100% successfully. We are using HP Blade Servers and HP EVA 4400 storage in our testing environment.
I also advise you to make an upgrade plan before performing the actual upgrade. Read all the stuff you can get and document current configuration and check which guests must be upgraded depending on their workloads.
Several reports have reached me with cluster validation errors after the upgrade. If you get these, leave a comment under this blog (with a short description of your server/storage config).
See also this thread on the Windows Server – High Availability (Clustering) Forum about the Cluster Validation errors with SP1:
Update 3/29/2011: Problem has been acknowledged by Microsoft. They are working hard to create a fix as soon as possible