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.
While we at Altaro always try to keep you all up to date on the latest dealings in the world of Hyper-V and Microsoft virtualization, sometimes there is such a wealth of information released or a large group of product releases that at times it just helps to get it all out there!
Therefore, I’ve prepped 10 useful links below that i hope you will find useful in your IT adventures!
In our article on common Hyper-V deployment mistakes, one item we discussed was the creation of too many Hyper-V virtual switches. This article will expand on that thought and cover various Hyper-V virtual switch deployment scenarios. One Switch will Usually Suffice The first and most important point to make is the same as mentioned in the earlier article: one virtual switch is enough for most Hyper-V hosts. We’ll start by showing how advancements in Windows and Hyper-V technologies address problems that necessitated multiple virtual switches in earlier versions. Native OS Teaming is Now Available In 2008 R2 and earlier, you could only team network adapters by using software provided by the network card manufacturer. This software was often buggy and unstable. Furthermore, Microsoft would not officially support any system that used such teaming. In those situations, Hyper-V administrators would often choose to leave the physical adapters unteamed and create multiple… Read More»
New year, new products! Some time in 2015, we’re all going to be graced with the newest edition of Windows and Windows Server, and along with them, Hyper-V. I wish I had a slick code name to give you, like “Viridian”, but it seems like most in-progress Microsoft products are now just code-named “vNext”. I’ve spent some time going over the published feature list. Some of the introductions will be very welcome. Some make me a bit less than enthusiastic. Sole Sourcing I’ve been burned more than once by writing about pre-release features and software conditions, even within a few months of release. The next version of Hyper-V is still quite a ways away, so there is still time for significant change. To that end, I’m only going to work with the officially published material on Hyper-V. Even that material could still be considered malleable at this point, but, in… Read More»
Like any creative work, a blog post is never really done; it’s just abandoned. Unlike many other mediums, blogs do allow us to easily refresh those older articles, but we so rarely ever do it. To close out this year, a few of us on the editorial team got together and selected a few highlights from the past year. Our 14 selections from 2014 (in no particular order): Hyper-V Guest Licensing This was our first licensing article directly related to guest licensing. We followed it up with a downloadable eBook that was expanded to include a number of examples, and Andy Syrewicze and Thomas Maurer gave a fantastic webinar on the topic. We’ve received quite a few questions and some great feedback. Keep an eye out for a follow-up post that takes on some of those questions and incorporates some of the suggestions. If you’ve got questions or suggestions of… Read More»