Powered by System Center
Posts tagged Update
Now that SP1 is finished it is time to upgrade both our physical servers and virtual machines with Windows Server 2008 R2. Be aware that your Virtual Machines should be either upgraded to SP1 or upgraded with the latest Hyper-V Integrations if you want to use new features such as Dynamic Memory or RemoteFX.
Checking your Hyper-V Integration Version
One way of checking the IC version is by looking at the Driver version of the Microsoft Virtual Machine Bus Network Adapter in Device Manager
See my Hyper-V.nu partner blog for more details:
In October 2010 HP published a customer advisory, warning for cluster resource failures in large Microsoft Windows 2008 and R2 clusters using multiple host NICs with HP P4000 SAN and its Device Specific Module (DSM) for MPIO.
If any combination of cluster nodes, MPIO NIC ports and storage nodes resulted in more than 31 iSCSI sessions per volume, these issues would surface. Cluster Validation tests would in fact fail in these configurations. Adding a cluster node or storage node without validation would fail or only partly work.
HP published a firmware update with patch 10085-00 increasing the number of iSCSI sessions from 31 to 64. HP promised to solve this problem in its next major release of P4000 SAN/iQ software.
The formula for calculating the number of iSCSI sessions is:
# of Microsoft cluster nodes *
( # of initiator NICs per cluster node * # of storage nodes)
Now that SAN/iQ 9.0 has been released we can see that HP has followed up on this issue:
A HP Support document released in December 2010 states that with the new release, it has solved problems with SCSI Persistent Group Reservation (PGR) by increasing the limit to 256 iSCSI sessions per volume. This number is high enough to cope with 16 cluster nodes and 8 storage nodes with two iSCSI network adapters. This adds up to 16 x 2 x 8 = 256: so still be careful with bigger configurations.
On October 12, 2010 Microsoft released security bulletin MS10-086 which resolves a privately reported vulnerability in Windows Server 2008 R2 when used as a shared failover cluster.
The vulnerability exposes the administrative shares of failover cluster disks. Non-clustered Windows 2008 R2 servers are NOT affected.
More information can be found here:
In the following location you can find a complete collection of System Center Virtual Machine Manager 2008 R2 updates. The list is divided into several sections for different configurations:
However it does not make mention of the latest hotfix rollup which appeared recently:
If you see prolonged startup time with Windows Server 2008 R2 servers with the Hyper-V role enabled, this can be caused by a large registry hive that increases after every backup.
“The issue occurs because of a large number of orphaned registry keys. The Volume Shadow Copy Service (VSS) snapshots create many registry keys. However, they are not deleted after the VSS snapshot operations are completed.”
The solution is hotfix KB982210: http://support.microsoft.com/kb/982210
Some time ago I asked MS to split the list for Hyper-V updates in R1 and R2. Well … they did and thanks a lot!
Hyper-V Update List for Windows Server 2008 R2:
Hyper-V Update List for Windows Server 2008:
Update April 2010:
A recent hotfix was made available by Microsoft as a workaround for a problem with Live Migration win AMD Family 10h processors.
When you run Windows Server 2008 R2 Hyper-V on a computer that uses AMD Family 10h processors, the host computer may restart unexpectedly or stop responding. When the computer restarts or stop responding, you receive no error messages.
This issue may occur when the Live Migration feature is used to move a virtual machine (VM) from one Windows Server 2008 R2 Hyper-V-based node to another node. This problem usually affects the source node that is the original location of the VM and usually does not affect the target node that is the new location where the VM will be moved.
Note This issue may occur in other scenarios and occurs not only in Live Migration scenarios.
Look for erratum #383 in this AMD support document
Thanks to IT Core Blog
A hotfix rollup is now available for System Center VMM2008 R2 which is part of the February 9 update.
List of issues that are fixed
Consider the following scenario:
- A user is a member of the Self-Service User role.
- A new virtual machine is created, and the user is assigned the owner of the virtual machine.
In this scenario, the user cannot connect to the virtual machine by using the Self-Service Portal.
Consider the following scenario:
- A highly available virtual machine is offline.
- Quick Storage Migration is used to move the offline virtual machine to another storage location that is in the cluster.
In this scenario, the virtual machine does not migrate to another node that is in the cluster by using Quick Migration or Live Migration after Quick Storage Migration is used.
VMware virtual machines are not listed in the Virtual Machine Manager console if there are duplicate custom named tags in VMware Virtual Center.
Consider the following scenario:
- A new virtual machine is created, and the owner of the virtual machine is a member of the Self-Service User role.
- While the create virtual machine job is running, a user is added or removed from the Self-Service User role.
In this scenario, the user is not added or removed from the Self-Service User role because the create virtual machine job is running.
This rollup also includes the resolutions that are documented in the following article for a Virtual Machine Manager 2008 R2 hotfix rollup package:
976244 (http://support.microsoft.com/kb/976244/ ) Description of the System Center Virtual Machine Manager 2008 R2 hotfix rollup package: November 10, 2009
After the hotfix rollup package is installed on the Virtual Machine Manager server, update the VMM agent on the Hyper-V and Virtual Server hosts.
Install at least these two hotfixes on Hyper-V R2 servers:
KB975354 A Hyper-V rollup package dealing with parallel backups on same cluster shared volumes and VM’s hosted by different servers; Avoiding data truncation as a result of simultaneous backup of VM from host and from within virtual machine; properly restoring a VM with snapshots to another location
KB975921 You may be unable to perform certain disk-related operations after an exception when a hardware provider tries to create a snapshot in Windows Server 2008 R2 or Win 7.
Although not specifically related to Hyper-V and DPM2010, I also install hotfix KB974909 which solves loss of the network connection within a virtual machine with heavy outgoing network traffic and many concurrent network connections. This could easily be the case when a VM level backup is being conducted.
There is also a list of tested hardware VSS providers:
I may have a chance to test the HP LeftHand VSS hardware provider, which is not yet on this list. The HP EVA 4×00, 6×00 and 8×00 is on the list by the way.
A comprehensive list of Windows updates and hotfixes for Hyper-V and Hyper-V R2 can be found here:
If you need to update your Hyper-V servers, you might just as well include this recent security update:
Microsoft Security Bulletin MS10-010 – Important
Vulnerability in Windows Server 2008 Hyper-V Could Allow Denial of Service (977894)
When you try to protect VM’s on a Hyper-V R2 clusters with DPM2010 RC you now get a warning if the required hotfixes are not installed.
This is very helpful!