What’s the difference between Generation 1 and 2 VMs in Hyper-V? What are the benefits of Gen 2? Should I use Gen 2 VMs? How do I convert?
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!
Microsoft Virtual Machine Converter (MVMC) allows you to convert VMware virtual machines and physical computers to Hyper-V virtual machines.
Ideally when backing up and copying a VHD from a running VM you use your backup software, but you can also export the VM or copy the file manually.
We’ve had quite a few posts about Hyper-V checkpoints lately (formerly snapshots). We also spend a fair bit of time warning people not to tinker with them manually. There are still those people that are going to tinker despite any warnings, and there will always be those people who don’t even find the warnings until they’re too late to be of any value. The least I can do is provide a tool that can be of use to anyone that’s stuck working on a complicated tree of differencing disks.
Virtual hard disks are usually created along with their owning virtual machines or, when a disk new is needed for an existing virtual machine, directly from the VM’s property sheet. There are times when you’ll want to connect an existing virtual disk, though. This post explains how to attach an existing virtual disk to a vm using Hyper-V Manager
Hyper-V is no longer the newcomer in the virtualization space. After springing forth from its Virtual Server parent, it’s now had over half a decade to mature into the reliable, enterprise-grade hypervisor that it is today. As with any complex software, Hyper-V is composed of many parts, like the branches and leaves of a great tree. Like a tree, some of those branches form into major trunks that define the tree’s silhouette. Others become a twisted impediment to the proper growth of the larger organism and must be pruned away for its overall well-being. In Hyper-V, one of those latter branches is the pass-through disk. Many of you are already aware of this fact and have long since moved on. The reasoning behind this post is that there are still a handful of people out there clinging to this old tech, wishing that branches that were solid in 2008… 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»
Bringing a physical operating environment into Hyper-V can be a challenging task. It is recommended that you use some application-level migration rather than trying to convert a physical operating system installation directly. However, some systems do survive the transition well. One tool that can be used in conversion operations is Sysinternal’s Disk2VHD. What is Disk2VHD? Disk2VHD is a software solution provided by Sysinternals. It reads the boot information, partition information, and data regions of a physical hard drive and produces a corresponding VHD or VHDX file. It is very important to understand that this is not a true physical-to-virtual conversion. The operating system is not prepared to run inside a virtual environment, nor is any cleanup work done on the source system to improve the odds of a successful migration. Microsoft Virtual Machine Converter 3.0 Before using this Disk2VHD to attempt a P2V, you might try Microsoft’s Virtual Machine… Read More»
Starting with Windows Server 2012 R2, it is possible to re-size a Virtual Hard Disk for a running Virtual Machine on Hyper-V! It was not possible to do so before for an online Virtual Machine running on Windows Server 2012 and earlier Hyper-V versions. Let’s have a look at some of the benefits this feature offers and requirements before you dive in and use it.
There are two topics I’m going to explain in this article (1) why you can’t relocate paging file to a Virtual Hard Drive connected to a SCSI Controller in Hyper-V running on Windows Server 2012 and earlier versions and (2) how you can utilize the new booting architecture introduced in Windows Server 2012 R2 to relocate paging file to a SCSI Controller.
One of the great unsung heroes of virtualization is the thin-provisioned virtual disk, known in Hyper-V terms as a Dynamically Expanding VHD. To say that it doesn’t receive its proper due is an understatement. It is more accurate to say that it is unjustly vilified and unfairly cast aside as useless technology. This post will defend this valuable tool.
Hopefully, every single technology professional in the entire Windows world knows that a VHD file is what Hyper-V uses as a virtual hard drive for Hyper-V guests. But, what else can be done with them? Be aware that “VHD” was the original extension for Hyper-V virtual hard disks. The more recent format is “VHDX”. Unless otherwise noted, I will use “VHD” to mean both types throughout this post. Revised January 3, 2015