Today Brad Anderson announced the availability of Virtual Machine Manager 2012 beta which can be downloaded for evaluation purposes. In an email from Carmen Summers who is Program Manager for Virtualization & Datacenter Management, it was stressed that VMM 2012 Eval should not be used for production.
Monthly archives for March, 2011
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:
This begins to look like a serial story. Hyper-V and NIC Teaming. Ever since I wrote a blog on using native VLANs with HP NIC Teaming and Hyper-V, I have been reluctant to try new versions. Now that Windows Server 2008 R2 SP1 was published almost a month ago, I have attempted to evaluate the consequences for this lovely combination.
Let me begin with referring to my blogs on NIC Teaming:
As from HP Network Configuration Utility (NCU) 10.10.0.x it is possible to use native VLANs in combination with Hyper-V without going through the hassle of manually adding multiple VLANs on the team and creating Hyper-V virtual networks and string those two together. By using a team setting called Promiscuous Mode we only had to make sure VLANs were known on the trunk and we were able to apply a VLAN ID to the virtual network adapter in the Hyper-V guest.
I have tested a couple of combinations:
TESTED CONFIGURATION 1
Config: Windows Server 2008 R2 SP1 with NCU 10.10.0.0 and Broadcom 5.2.22.x drivers from HP PSP 8.60 but without teaming configured. VLAN configured on adapter itself.
Result: Guest can communicate with network. VLANs are passed through correctly.
Conclusion: Although you have no network redundancy in this configuration, it is easy to add a VLAN id to the vNIC in the guest. Promiscuous mode is not applicable here.
TESTED CONFIGURATION 2
Microsoft seems to make the beta of System Center VMM 2012 available on Technet very soon. I just checked this page and saw a (still broken) link to the download of what we formerly referred to as Virtual Machine Manager vNext:
On March 21st 2011, Microsoft Management Summit 2011 will kick off in Las Vegas, sold out with about 5000 visitors. Of course a great deal of focus will be on Hyper-V private cloud, Azure public cloud and those parts of System Center that manage the private, public or even hybrid cloud.
Although I have already spent a full day on VMM 2012 during MVP Summit two weeks ago, I will definitely visit the majority of presentations on this topic.