During a ask-the-experts at Microsoft Management Summit (MMS) 2011 in Las Vegas, a customer asked a question of how to utilize Microsoft Deployment Toolkit (MDT) 2010 Update 1 to install Windows Server 2008/R2 and enable the Hyper-V role. The customer had tried several things but to no avail as the customer was using ConfigMgr’s Operating System Deployment (OSD) feature and this wasn’t working. In today’s post, I thought I would share how to easily do this.
Aussie legend Cameron McBride and good friend Tony Sanchez from Citrix sent a heads up to me recently on some performance related hotfixes. They are specific to proc and SP1. Nevertheless they are definitely worth applying for the best performance.
Issue 1: Performance is not as awesome as it could be on Westmere or Sandybridge chipsets
- You have a Windows Server 2008 R2-based computer that has a large amount of physical memory and that has Intel Westmere or Sandy Bridge processors.
For example, you have a computer that has Intel Xeon 5600 series processors and that has 48 gigabytes (GB) physical memory.
- You install the Hyper-V role on the computer.
In this scenario, the performance of the computer may decrease.
For example, the following performance issues may be encountered:
- The CPU usage is high and the server responds slowly when you copy large files on the computer. For example, you copy a 10-GB file.
- The disk I/O performance of the virtual machines (VMs) is slow.
- Windows takes a long time to start.
Issue 2: Networking Performance is not as awesome as it could be under load and is lost in certain scenarios
You install the Hyper-V role on a computer that is running Windows Server 2008 R2 Service Pack 1 (SP1).
- You run a virtual machine on the computer.
- You use a network adapter on the virtual machine to access a network.
- You establish many concurrent network connections. Or, there is heavy outgoing network traffic.
In this scenario, the network connection on the virtual machine may be lost. Additionally, the network adapter may be disabled.
- You must restart the virtual machine to recover from this issue.
- This issue can also occur on versions of Windows Server 2008 R2 that do not have SP1 installed. To resolve the issue, apply the hotfix that is described in one of the following Microsoft Knowledge Base articles:
974909 (http://support.microsoft.com/kb/974909/ ) The network connection of a running Hyper-V virtual machine is lost under heavy outgoing network traffic on a Windows Server 2008 R2-based computer
2264080 (http://support.microsoft.com/kb/2264080/ ) An update rollup package for the Hyper-V role in Windows Server 2008 R2: August 24, 2010
So theres hotfixes for both of these. Thanks Cam and Tony for the heads up on this!
This whitepaper demonstrates why organizations should choose Microsoft® Hyper-V™ as their hypervisor when designing and implementing a Virtual Desktop Infrastructure (VDI) solution.
Choosing a hypervisor for deploying a VDI solution involves a number of important considerations, each of which can be fulfilled by using Microsoft’s Hyper-V 2008 R2 SP1 hypervisor-based virtualization technology. When implemented together with the Microsoft System Center family of products and desktop virtualization technologies from partners like Citrix, organizations can build integrated VDI solutions that can meet the needs of your business while keeping costs under control.Based on the results obtained from internal testing and because VM density has a significant influence on datacenter cost structures; an integrated Citrix/Microsoft VDI solution that includes Microsoft Hyper-V 2008 R2 SP1 and System Center delivers unique end-to-end business value for organizations planning on implementing VDI.
Someone had some questions about Hyper-V today and this link was given. WOW. Talk about the mother load of information!
This is a list of Hyper-V resources you can add too, and feel free to rearrange. Just click the "Edit" button above the article. For organization ideas, and other important links, see:
Microsoft Virtualization Community, because virtualization at Microsoft involves a lot more than Hyper-V.
Nice post over the TechNet blogs from Ken Lince.
Didn’t think you could boot Hyper-V from a USB? Well, you can.
Yeah, kinda snuck up on me too – I knew this was a feature request but it fell off my radar as it’s not something that I’ve had a need for and quite frankly, no one has asked me about it in any of the dozens of sessions that I’ve done on virtualization to partners and customers since R2 was released. But, after a conference call last week when this topic came up, I thought I better go do some due diligence to see where we were. Sure enough, this is fully supported now.