hyper-vhyper-v-server-2008-r2stoperrorwindows-server-2016
I'm trying to create a Windows Server 2016 instance on Hyper-V 2008 and it fails to boot from the ISO because of a stop error "MACHINE CHECK EXCEPTION". Is installing 2016 not possible on an OS as old as 2008 R2?
I've tried installing the same ISO on Windows 10 HyperV and that works OK.
Is the only solution to upgrade the host OS to a later version?
Well, this is a strange means.
The key thing is Windows/Hyper-V is referring to a "list" somewhere to tell it what virtual machines are registered with the server. My virtual machines are scattered across multiple drives, so there has to be a centralised repository. Which turns out to be
C:\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines
there are symbolic links that refer to the physical locations of the actual config XML files. I noticed the troubled VM links had a "lock" icon.
I edited the security ACL of the troubled symbolic link. Sure enough it does not have the NT Virtual Machine account like the rest, so instead I granted it Full Control to the Users group. Restarted Hyper-V Virtual Machine Management service, and it could once again load up the missing VMs. It appears to work without the Virtual machine accounts.
Still haven't gotten the complete deep answers I was looking for to explain just what Hyper-V is requiring out of those Virtual machine accounts, but at least the original virtual machine config can be reused.
The short answer is SCVMM.
It's a product Microsoft makes for expanded management of Hyper-V VMs, however it has a very nice web portal that can have permissions delegated down to the individual VM level if desired. Start, restart, pause, and Snapshot are some of the capabilities that can be delegated. The one you're most concerned about is Console access through RDC and it can be allowed through the web portal as well.
Best Answer
According to the official document, Server 2016 is not a supported guest OS on Server 2008 R2:
https://technet.microsoft.com/en-us/library/cc794868(v=ws.10).aspx
You need Server 2012 R2 or Win8.1 Hyper-V host:
https://technet.microsoft.com/library/dn792027.aspx