This tutorial shows you how to get the best Hyper-V performance out of your Dell PowerEdge T20 hardware through tweaking a number of configurations from network settings to storage performance.
Understand industry-standard terminology around backup and how to apply it in a Hyper-V environment! Learn the language of virtualization backup.
Having trouble deleting virtual hard disks left behind when you delete a virtual machine? Eric has a simple fix that will help you delete a VHD from a clustered shared volume!
Hyper-V virtual machines are defined by an XML file. Eric discusses the importance of XML files, how Hyper-V uses them, and why you should leave them alone.
It is possible to connect the host’s physical optical drive directly to a virtual machine for the purpose of loading operating systems and software, but, unless the host is right next to you, it’s not very practical. The obvious solution is to use images of the necessary discs. Hyper-V makes some of that easy, but using it across a network connection can be somewhat more difficult. This post will examine your options.
It’s not difficult to find all sorts of lists and discussions of best practices for Hyper-V, however best practices lists are a bit tougher to find for failover clustering. What I’m going to do in this article is focus in on the overlapping portion of the Hyper-V/Failover Cluster Venn diagram, resulting in my 19 best practices for a Hyper-V Cluster.
My standing recommendation on allocating virtual machine resources is to start small. It’s very easy to grow almost all virtual resources with very little, and sometimes no impact. Taking resources away, on the other hand, can be trickier. The most difficult resource to remove from a virtual machine is drive space. If it’s just a matter of removing a disk, that’s usually not so bad. Making a virtual disk smaller is somewhat trickier.