Friday, July 6, 2018

Creating a Hyper-V Virtual Machine

In this post, I will create a Hyper-V virtual machine to hold a future installation of Windows Server 2016.
First, we will need to enable Hyper-V to be able to install the Hyper-V Manager.

Here's what Hyper-V looks like just after installation, before anything has been configured:

Once Hyper-V Manager is installed and running, click "New" in the right-hand pane, then "Virtual Machine..." You will then see this dialog:
This first screen asks for a name for the virtual machine, as well as whether or not you would like to store it somewhere other than the default location in C:\ProgramData\Microsoft\Windows\Hyper-V. Enter the correct settings, then click "Next."

Here, you can choose which generation of virtual machine you want to create. As the choices indicate, Generation 2 VMs support more and newer features, but won't work with a 32-bit guest OS. In this case, since I'm installing Windows Server 2016 64-bit, I will choose Generation 2. Select your generation of virtual machine, then click "Next."

On the next dialog, you can decide how much memory you would like to allocate to the VM. Checking the box for "Use Dynamic Memory for this virtual machine" allows Hyper-V to increase or decrease the amount of RAM dedicated to the VM based on its needs. This allows optimal use of the host's memory; rather than gigabytes of RAM sitting unused by the VM, but unavailable to the host, Dynamic Memory allows the host to give that RAM to other processes or VMs that will be able to utilize it. 
For my virtual machine, on which I don't intend to run anything particularly resource-intensive, 2 GB will be enough. Enter the amount of memory you need, choose Dynamic Memory or not, then click "Next."


If you have already set up a virtual switch or other virtualized networking in Hyper-V Manager, you now have the opportunity to set this VM to be connected to that. I have not yet done so, so I will use the Default Switch for now. Select the network connection for the VM, then click "Next."

On the next dialog, you can create a new Virtual Hard Disk (VHD, extension .vhdx), select an existing VHD file (if you are installing a virtual machine that has already been set up), or choose to attach a virtual hard disk later (if you are running a Linux live CD image, or any other use case that does not immediately need persistent storage). Windows Server 2016 requires at least 32GB of hard disk space, so I will create a new 64GB VHD to allow plenty of room for growth. Select your options, then click "Next."

Next, you can choose to select installation media, to boot from a network-based source, or not to install anything yet. Select the option that you want, then click "Next."

You will see a summary screen listing all of the options you have chosen. Verify that these are correct, then click "Finish", and see that your VM is now available in Hyper-V Manager:

In the next post, I will start this new VM and will install Windows Server 2016.

No comments:

Post a Comment

Tableau, TabPy, and the Case of No Input Rows

 I haven't scientifically confirmed this or anything, but it sure seems like if you pass an empty dataframe to a TabPy script, then no m...