Back on the 10th of Dec. some of you may recall that Thomas Maurer and I did a webinar on Scripting and Automation in Hyper-V. We had a number of questions throughout the webinar that we were not able to get to due to time constraints, but I’ve compiled a list of some of the most ask about questions below and what their answers are.
Original post: Scripting and Automation in Hyper-V – Webinar Follow Up
Yesterday we released the Microsoft Virtual Machine Converter 3.0. You can download it here: http://www.microsoft.com/en-us/download/details.aspx?id=42497
It has a staggering amount of features. Including the ability to convert physical computers to virtual machines and to convert VMware virtual machines to Hyper-V virtual machines online and offline.
I have been asked this question a couple of times recently. The odd thing, to me anyway, is that most of the people who have asked me have stated:
I read this article: http://msdn.microsoft.com/en-us/library/cc794868(v=ws.10).aspx about supported guest operating systems for Windows Server 2008 R2, and did not see Windows Server 2012 R2 listed. Is it supported?
The answer is – no. That is why it is not listed.
Generally speaking, we make sure that the we support the release immediately after the host operating system (i.e. 2012 on 2008 R2, 2012 R2 on 2012, etc…). But we do not go beyond that.
If you really want to run Windows Server 2012 R2 in a virtual machine – I highly recommend that you upgrade your host first. Besides which, there are so many great new features in Hyper-V in Windows Server 2012 and 2012 R2 that you should want to take advantage of!
Dynamic memory is a great feature that allows Hyper-V administrators to get better utilization of their physical memory. But it can be hard to tell what is going on from inside of a virtual machine. There are, however, some things that you can do from inside a virtual machine.
The first thing you can do is see how much memory is currently available to your virtual machine. This is just the free memory as is displayed in Task Manager inside the guest operating system:
Beyond this, if you are running Windows 8 or later, you can also see what the maximum memory is set at for your virtual machine. In the screenshot above you can see that the Maximum memory of this virtual machine is set to 4GB.
You can also access the information about the maximum memory configured inside of a virtual machine by looking at the Maximum Memory, Mbytes performance counter off of the Hyper-V Dynamic Memory Integration Service using Performance Monitor.
Finally, you can access this information using PowerShell:
Running the following command inside of a virtual machine:
(get-counter “Hyper-v Dynamic Memory Integration ServiceMaximum Memory, Mbytes”).CounterSamples.CookedValue
Will tell you what the maximum memory for that virtual machine is configured to.