Hyper-V Issues Resolved by Microsoft Windows Server 2008 Service Pack 2
1.0 Introduction
Service packs are a collection of updates to a product that resolve known issue or workarounds; they may also introduce new features or extended the capabilities of existing ones. Moreover, service packs update systems to the most current code base. Being on the current code base is important because that's where Microsoft focuses on fixing problems. For example, any such work done on Windows 2008 is targeted at the next service pack and hotfixes are built against the existing available base.
2.0 Hyper-V Fixes
The following list is some of the key fixes from the 829 issues that Service Pack 2 for Microsoft Windows Server 2008 resolves which relate specifically to the Hyper-V role:
|
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". |
|
Windows Server 2008 may restart unexpectedly when you open the Hyper-V manager console to manage virtual machines. |
|
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. |
|
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. |
|
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. |
|
Windows Server 2008 Hyper-V VSS writer is not used during a backup job because of corrupted or invalid virtual machine configuration files. |
|
A Hyper-V update is available to increase the number of logical processors and virtual machines on a Windows Server 2008 x64-based computer. |
|
Stop error message on a Windows Server 2008-based computer that has the Hyper-V role installed: "STOP 0x0000001A". |
|
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. |
|
An update is available for Windows Server 2008-based computers to address issues with backing up and restoring Hyper-V virtual machines. |
|
The IRET and IRETD instructions do not support the Nested Task (NT) flag in protected mode in a Windows Server 2008 Hyper-V environment. |
|
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. |
|
You cannot connect to a virtual machine when the Windows Server 2008 Hyper-V VMMS certificate has expired. |
|
The classic Start menu is not displayed correctly in Windows Server 2008 without Hyper-V |
|
Increased functionality and virtual machine control in the Windows Server 2008 Failover Cluster Management console for the Hyper-V role. |
|
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. |
|
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. |
|
Windows Server 2008 Hyper-V systems restart unexpectedly and you receive a 0x1000007E Stop error code when you mount a VHD file. |
|
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]". |
|
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. |
- xtravirt's blog
- Login or register to post comments
Spotlight:
VMware Documentation Downloader v11.08.30
Updated for vSphere 5 - A free tool for those on the move who need information FAST
vSphere 5 License Entitlement Changes
See what has changed in the license entitlement in vSphere 5?
Thin Client vs Zero Client
The differences between Thin and Zero desktop clients for VDI
