Hyper-V Dynamic Memory Allocation strikes again… I have decided to no longer use Dynamic Memory Allocation on any of my virtual machines. It is a fine idea in theory but it is extremely buggy and I am not sure how it made it into a production OS…
What’s the issue this time around? This is my third article talking about a bug related to Dynamic Memory Allocation. In this case it has to do with the clock sync on the VM. Which is a major ordeal if you happen to be working with a virtualized Domain Controller. Here was the situation… every time power got cut to the host and subsequently the VM was “hard powered” off, upon reboot the clock would be off by several hours. (more…)
Ran into a fun issue today… I had a pair of Server 2012 R2 servers in a remote office that refused to sync the proper time for their clocks. No matter what I did they were always off by five minutes. One of them was a domain controller for the office.
In the process of fixing the issue I learned about an interesting feature in hyper-v that was the root cause of all my trouble. By sharing my experience, hopefully you will avoid the same issues I ran into.
I had to reconfig my dysfunct home office network today but now everything is setup and talking correctly.
I received a 16 port unmanaged switch and 3 USB lan adapters today and all is working correctly with my 3 Server 2012 R2 boxes. The cluster can move forward as soon as I have some more time to work on it!
So part of my “poor-man’s hyper-v cluster” experiment in my home office here has led me to start looking into storage options for virtual platforms. Hyper-V is apparently quite flexible, however fail-over clustering limits your options.
So for those of you who are just joining us I am doing research on clustered Hyper-V for work. This was a self started project so I grabbed whatever I had available. I am therefore building an Active Directory managed network and a three node Hyper-V cluster using the following components…
Dell Latitude D830 Laptop – Intel Core Duo + 3 GB of RAM + 150 GB HD
Dell Latitude E6400 Laptop – Intel Core 2 Duo + 4 GB of RAM + 230 GB HD
Dell Optiplex 990 Mini-PC – This is my “top of the line” unit lol… Core i7 – 4 GB RAM – 160 GB HD
Ancient TP-Link N150 router – 4 wired ports of 100 mbit bliss… (no gigabit :(…)
Surprisingly enough, even the ancient D830 has a processor that is new enough to run Hyper-V 3.0 on Windows Server 2012R2. This will only work with the server version of the OS though because of no support for SLAT which is an added requirement of the CPU if you are going to run Hyper-V on Windows 8.1. Only the Core I7 has SLAT built-in.
Another interesting note, the E6400 with the Core 2 Duo was by far the biggest pain to get working. Hence I am noting it here for anyone that comes searching…
–NOTE ABOUT DISABLING TRUSTED EXECUTION ON DELL LATITUDE E6400 LAPTOP–
Can’t enable hyper-v role service on Dell Latitude E6400 laptop? Here is why… Trusted Execution needs to be TURNED OFF in BIOS. This is definitely a Dell specific glitch. So, reboot into bios, turn on the TPM, reboot, go into BIOS, ENABLE the TPM (two separate steps) and then under virtualization options turn on everything except for Trusted Execution. Then it will work. Okay… moving on…
Okay… this was supposed to be a post about storage. So lets talk storage.
I have a stack of old laptops sitting here from work (I occasionally get the old ones back when they are retired). It occurred to me that laptops would make a very good “home server stack” environment. Here is my reasoning…