I’ve copied the listing of Hyper-V hot fixes that are included in Windows Server 2008 Service Pack 2.
- KB953585 – Error message when you try to start a Hyper-V virtual machine on a Windows Server 2008-based or Windows Vista-based computer that uses the NUMA architecture: "An error occurred while attempting to change the state of virtual machine VMNAME"
- KB959403 – Windows Server 2008 may restart unexpectedly when you open the Hyper-V manager console to manage virtual machines
- KB961730 – A memory leak occurs in the Vmwp.exe and Vmms.exe processes on a Windows Server 2008-based computer that has the Hyper-V role enabled
- KB967124 – Hyper-V performance counters in Windows Server 2008 are displayed incorrectly or report incorrect data when you remotely query the counters from a Windows Server 2003-based computer
- KB956589 – Description of the Hyper-V update for issues that may occur when you manage the Hyper-V role on the 64-bit editions of Windows Server 2008 by using SCVMM
- KB956697 – Windows Server 2008 Hyper-V VSS writer is not used during a backup job because of corrupted or invalid virtual machine configuration files
- KB956710 – A Hyper-V update is available to increase the number of logical processors and virtual machines on a Windows Server 2008 x64-based computer
- KB957967 – Stop error message on a Windows Server 2008-based computer that has the Hyper-V role installed: "STOP 0x0000001A"
- KB958184 – Virtual machine backup operations fail in Windows Server 2008 when Hyper-V virtual machine files are saved on a volume that is mounted on a failover cluster by using a volume GUID
- KB959962 – An update is available for Windows Server 2008-based computers to address issues with backing up and restoring Hyper-V virtual machines
- KB960578 – The IRET and IRETD instructions do not support the Nested Task (NT) flag in protected mode in a Windows Server 2008 Hyper-V environment
- KB963709 – The AltGr key does not work on a Linux virtual machine on a Windows Server 2008-based server that has the Hyper-V role enabled
- KB967902 – You cannot connect to a virtual machine when the Windows Server 2008 Hyper-V VMMS certificate has expired
- KB950612 – The classic Start menu is not displayed correctly in Windows Server 2008 without Hyper-V
- KB951308 – Increased functionality and virtual machine control in the Windows Server 2008 Failover Cluster Management console for the Hyper-V role
- KB953828 Windows Server 2008 Hyper-V virtual machines generate a Stop error when NLB is configured or when the NLB cluster does not converge as expected
- KB958065 – You cannot configure a Hyper-V virtual machine by using Windows Server 2008 Failover Clustering when the virtual machine uses a storage device that is managed by a third-party clustered file system or a third-party replication solution
- KB959766 – Windows Server 2008 Hyper-V systems restart unexpectedly, and you receive a 0x1000007E Stop error code when you mount a VHD file
- KB959978 – Error message when you back up a Windows Server 2003-based virtual machine on a Windows Server 2008 Hyper-V-based computer: "GetWriterStatus FAILED for Selected writer [Microsoft Hyper-V VSS Writer], writer is in state [9] [VSS_WS_FAILED_AT_FREEZE]"
- KB960038 – You receive a "0x0000007E" Stop error on Windows Server 2008-based computers that host Hyper-V virtual machines when you use the Hyper-V writer to back up virtual machines
I’ve also copied out the included hotfixes for failover clustering that I thought would be relevant in a fault tolerant Hyper-V Cluster:
- KB948720 – You cannot install device drivers in a Windows Server 2008 cluster environment if the drivers contain LZ-compressed files
- KB950811 – The Windows Server 2008 failover cluster cannot start because of a deadlock condition in the Cluster service
- KB955733 – Incorrect status codes that are returned in failover clusters may cause operations to fail on a Windows Server 2008-based computer
- KB950181 – When you stop a node in a Windows Server 2008 failover cluster, the groups that are hosted on that node may fail over to a random node instead of to the next available node
- KB950267 – The Cluster service may stop responding on a Windows Server 2008 cluster node when an application performs VSS backup of files from a volume
- KB952247 – The Cluster network name resource and the File Share Witness resource may not come online on a Windows Server 2008 failover cluster node if a disjointed namespace is configured
- KB953652 – A physical disk resource may unexpectedly fail or go offline when the IsAlive function is executed on a Windows Server 2008 cluster node
- KB956891 – Error message when you create a cluster on a Windows Server 2008-based computer that uses a third-party DNS server: "The network name {0} is already used in the network"
- KB958983 – Error message when you use the Windows Server 2008 Failover Cluster Management console together with a Windows Server 2008 SP2-based failover cluster: "This feature is only supported with Windows Server 2008 Enterprise and Datacenter servers"
- KB960334 – The Windows Server 2008 and Windows Vista Failover Cluster Validation process fails, and you receive an error message when the "System cryptography: Use FIPS compliant algorithms for encryption, hashing and signing" policy is enabled
- KB963702 – A Windows Server 2008 Failover Cluster that has a MPIO solution may encounter stop code 0x0000007E or 0x000000D5 during a path failover
- KB949961 – Scheduled shadow copy creatio
n tasks do not run on a clustered Windows Server 2008 file server after a failover occurs - KB954475 – After you restore a clustered disk from a VSS transportable hardware snapshot in a Windows Server 2008 cluster, the clustered disk cannot come online
- KB955656 – You cannot restore a VSS transportable snapshot to some LUNs different from the original LUNs in a Windows Server 2008 cluster
- KB967560 – A backup operation fails on a two-node failover cluster that is running Windows Server 2008 after one of the disk resources is moved