Download.
Network Emulator Toolkit 32-Bits.
Network Emulator Toolkit 64-Bits.

There is a new version of this tool, see the comment from Lonny Kruger. He wrote a blog about it. http://blogs.msdn.com/lkruger/archive/2009/06/08/introducing-true-network-emulation-in-visual-studio-2010.aspx

The HP Sizer for Microsoft Hyper-V 2008 R2 is an automated, downloadable tool that provides quick and helpful sizing guidance for “best-fit” HP server and storage configurations running in a Hyper-V R2 environment. The tool is intended to assist with the planning of a Hyper-V R2 virtual server deployment project. It enables the user to quickly compare different solution configurations and produces a customizable server and storage solution complete with a detail Bill of Materials (BOM) that includes part numbers and prices.

The HP Sizer for Microsoft Hyper-V 2008 R2 allows users to create new solutions, open already existing solutions, or use other types of performance data collecting tools, such as the Microsoft Assessment and Planning tool (MAP), to build rich Hyper-V R2 configurations based on HP server and storage technology. The tool allows rapid comparison of Hyper-V R2 characterizations using various HP server and storage choices.

Customers often ask “Given a hardware load-out X, how many Ys can I get/run/host?”

The frustrating answer always starts with “…it depends…”. We caveat this way not because we want to frustrate, but because it is true. Many teams will go on to say “We have tested the following in our labs and gotten the displayed results…”

1 X = thingy

2 X = more thingies

3X = many more thingies

While accurate, not super-helpful.

The truth is that to do good perf planning for Hyper-V you have to run some tests.

Run them using your actual production load (converted to Virtual Machines) in a test environment.

TIP: you can download the free VHD version of SCVMM, then run it as a VM to convert your production machines to “test” virtual machines.

Then play with your assumptions and tweak things higher and lower and to your design tolerance and actually observe how perf goes.

Add an overhead/forgot-to-test percentage, done.

So, how to do that for Hyper-V? Here are some perf testing resources to help you:

• Performance and capacity requirements for Hyper-V
• Hyper-V Performance FAQ
• Measuring Performance on Hyper-V
• Checklist: Measuring Performance on Hyper-V
• Performance Tuning Guidelines for Windows Server 2008
• Performance Testing Guide for Windows Paper
• Optimizing Hyper-V performance: Advanced fine-tuning
• Hyper-V Support, Performance and Load Tools
• Hyper-V How To: Set Up a Virtualization Test Lab using Windows Server 2008 Cluster, Hyper-V and simulated iSCSI…
• Hyper-V Server Sizing: How Much Memory for the Host?
• VM Perftuning: Minimize VM background processing
• Hyper-V How To: Balance VM I/O
• Monitoring Hyper-V Performance
• How to get Processor Utilization for Hyper-V via WMI
• Hyper-V Performance Counters – Part one of many – The overview
• Hyper-V Performance Counters – Part two of many – “Hyper-V Hypervisor” counter set
• Hyper-V Performance Counters – Part three of many – “Hyper-V Hypervisor Logical Processors” counter set
• Hyper-V Performance Counters – Part four of many – “Hyper-V Hypervisor Virtual Processor” and “Hyper-V Hypervisor Root Virtual Processor” counter set
• Hyper-V Performance Counters – Part five of many – “Hyper-VM VM Vid Numa Node