This server, despite being on the Microsoft HCL as certified for Windows Server 2016 (see https://www.windowsservercatalog.com/item.aspx?idItem=5034ab7d-e864-6747-9e38-df974f397de7&bCatID=1282 ) )doesn't seem to support the Hyper-V role.
I have tried the following scenarios (note, all firmware is as up to date as possible):
Installed Windows Server 2016 using intelligent provisionsing;
Installed Windows Server 2016 without intelligent provisioning;
Installed bare metal Hyper-V 2016.
In all cases, I've tried using both the drivers shipped on the provisioning AND the latest drivers from the HPE supprot site.
In every case, the role will go through the initial add, will reboot, reboot again and hang at the Windows logo with a spinning wheel.
Safe boot works but removing the role from there results in it saying feature couldn't be completed at which point it reboots back into the same hung condition.
A logged boot shows the last file loaded to be FASTFAT.SYS. Renaming this in both the DLL cache and SYSTEM32\drivers folder just shows the same point with the exception that FASTFAT failed to load.
In a nutshell the server doesn't appear to be in any way comaptible with Hyper-V 2016 OR I just have a bad one.
Wouldn't mind if anyone else could test and let me know their results.
Oh it's the onboard BL210 Array Controller with a pair of 1TB SATA drives (all checks out in good condition). Same results whether using the very latest 2016 compatible driver or the older 2012 R2 driver.
This is just a lab machine but I'm now at the point of not wanting to risk 2016 on it, trashing my lab down the line if I added another role that turns out to screw the OS over. :(