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.
Creating and managing VDI are not trivial tasks in Hyper-V (or any other hypervisor) and can end in disaster if not properly planned. My goal with this article is to reach you during the contemplation phase where you’re trying to determine if VDI is worth tackling.
Here are 7 things to think about before even starting a pilot project.
Replica is one of the many compelling features of Hyper-V. It allows you to create a comprehensive disaster recovery system with very little effort. It’s simple to design and deploy. What’s not always so easy about Hyper-V Replica is understanding many of its constituent components and some of the operations. In this article, the focus will be on the Replica Broker.
Most titles like that requires some clarification. I would hope that, to anyone that has read even a little of my work, it’s obvious that I’m not anti-Microsoft. The vast majority of technologies that I work with at my regular job are from Microsoft. However, I strongly believe that my pragmatism must always be tempered by my realism, and the realist in me insists that regardless of how much I depend on something, I must always remain aware of its flaws. So, in this post I’m going to talk about the larger things I believe that Microsoft should truly be doing differently with Hyper-V. In simple terms, these mainly boil down to backward compatibility.
If you’re administrating a Hyper-V cluster that is a few years in age and you’re thinking of expanding, you might be at the point where it is no longer feasible to purchase a new host with hardware that matches your existing hosts. However, if the CPU on the newer host is of a different version or generation, live migration or restoring a saved state VM between the new and old host will fail. Luckily, Hyper-V comes with a feature called CPU compatibility mode that will allow these functions to continue between CPU generations.
Are there any bumper stickers or t-shirts out there that say, “I was using Hyper-V before using Hyper-V was cool?” If there are, I think I need one. I built my first production system on Hyper-V 2008 R2 not long after it debuted. So, I missed the early-adopter crowd by a couple of years but I’ve definitely been in this for a while. The only problem with sticking with a tech as it grows from infancy is that sometimes things change and you miss out. One of the things that changed on me was the way that time synchronization works between Hyper-V and its guests.
When creating a Hyper-V checkpoint, it is crucial to know where the checkpoint files are being saved, especially since checkpoint files can fill up storage. When trying to find where the checkpoint files are being stored in your Hyper-V environment, it is important to understand what types of files are generated when creating a checkpoint. This is because components of the checkpoint are stored in two separate locations. The AVHDX file is stored with the VHD storage and the checkpoint configuration files are stored with the VM’s active configuration files.
One of the first things to check for whenever using a snapshot or checkpoint in Hyper-V is the available storage in the location where checkpoints are being stored. If enough space is available, the next thing to verify is how long the checkpoint is going to be left in place. Verifying the proper storage for using checkpoints is an important step and following these two steps can save you from shame later if the environment you are working on has very little wiggle room as far as storage.
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!
Installing Hyper-V on a bare metal server is a relatively easy process. However, it can come with its headaches when dealing with driver issues. In this demonstration we will be installing Server 2012 R2 Hyper-V on an HP ProLiant server using the iLO (Integrated Lights-Out) out-of-band management console.
Exporting checkpoints is one of those features that is very handy but not commonly used since it’s pretty situational. For example, picture this scenario: let’s say we just applied an update to a VM and the update went south. Thankfully, we created a checkpoint of the VM before we did the upgrade and we can use that checkpoint to revert the VM.
Metering is one of those unpleasant yet essential parts of systems administration. If you don’t know anything about your systems’ resource utilization, you can’t properly design their replacements. If you haven’t been keeping track, you won’t be able to answer the question, “What happened” when things go awry. If you aren’t keeping a close eye, you won’t have any advance warning before something collapses in the middle of a major production cycle. When it comes to networking, you’re probably not going to believe how easy it is to get MRTG up and running.
Linux on Hyper-V is becoming more and more popular as Microsoft continues to increase their support for it. One of the nicest parts about it is the “It Just Works” aspect. For distributions that are less than a few years old, the Hyper-V Integration Components are built right in. There isn’t any time wasted fiddling with scouring the Internet to look for instructions on compiling or even scripting them in. For me, my interest was sharpened when my TechNet subscription expired for the last, non-renewable time. I could, and will, start using the evaluation copies of Windows Server for testing, but that expiration thing is pretty annoying. Sure, 120 days seems like a long time. Maybe for people in their 20s, it is. But, as I was working up my Linux examples, I noticed that I hadn’t even rebooted my test lab switch in about seven months. If you’d… Read More»
Accessing Hyper-V Manager can be quite a mystery if you’ve never launched it before or when you’re working in an unfamiliar environment. You don’t want to be stuck in the situation of frantically searching for Hyper-V Manager when a critical VM is down and needs attention.
There are different methods of accessing this tool and with the various flavors of Windows, it’s good to know where to look and how to install it for each one.