Hyper-V Program Manager
We have released a bunch of updated documentation in the last week.
The first thing to look at is the Live Migration Network Configuration Guide. The really neat part of this is that it talks through all the supported / unsupported network configuration options. It also talks how to use the network QoS support built into Windows in order to safely share network connections in such a configuration (this is a neat option that I often use in my demo setups):
The next thing to look at is a new Virtual Hard Disk performance white paper that we have released that analyzes the performance characteristics of virtual hard disks in Windows Server 2008 R2 and contrasts it to Windows Server 2008. Lots of interesting technical detail in here:
This somewhat relates to your last 2 posts wrapped into one question. If one is migrating from W2K8 Hyper-V to W2K8 R2 Hyper-V is it best to recreate the VHD files rather than just doing a straight copy so as to benefit from the enhanced default VHD block size of 2Mb? Do the migration tools just do a basic file copy or do they actually create a 'new' VHD file on the new destination sysetm?
The performance document is interesting... It would be even more interesting to evaluate the physical sub-structure of the disks supporting the VHD's.
It's always a chore to try and figure out the best drive combination/configuration when building a Hyper-V server.
Some example scenairos:
* What is the performance difference between a 5-disk Raid-5 vs a 5-disk Raid-10.
* What is the performance difference between using 3/5/7 disks in any given raid.
* What is the performance difference between an external USB enclosure vs. Firewire vs. eSATA enclosure.
The RAID performance questions are well documented on the internet. That deserves a "google it" link
USB vs a DMA storage device? Really? =D Maybe USB 3 will chance things, but this isn't so much as as a disk I/O issue as is it is a CPU overhead problem.
Thanks for the links!