Confused about Intel Virtualization setting in Bios

[Prax]

So little background, I have a Server 2008 R2 box with Hyper-V running a Home Server 2011 Guest OS. The hardware in the machine looks like this:
Proc: i5-2405S (Sandy Bridge)
Board: Intel DQ67EP
Mem: 4 gigs
Drives: 1 OS drive presented to 2008 host 4 Drives presented to hyper-V'ed guest machine

This machine had its motherboard and processor replaced but did not have an OS re install at the time. The OS booted and re detected all the new hardware and was able to start with no issues including the loading of the guest OS's.

I have updated the bios and all the drivers to their current versions.

So my question is this, there is a setting in the Intel Award Bios called "Intel® Virtualization Technology". If this setting is enabled the Intel Processor Identification Utility, Coreinfo (Microsoft Utility), CPU-Z all report that the board/processor combination DO NOT support any Virtualization technologies, and hyper-V guest machines will start. If I disable that option in the Bios all of the above utilities report that the board/processor combination DO support ALL Virtualization technologies, BUT no hyper-V guest machines will start they complain that a processor doesn't support it. Am I in need of an OS re install for hyper-V to detect the newer options on the board? Does disabling that bios option turn off all Virtualization but force the board to report the correct information?

Thanks,
Prax

P.S. I have been wanting to implement RemoteFX on this server, with the addition (or just running with the built in GPU on the chip, Intel 3000 HD) do I have enough hardware in order to drive it provided I have all the licensing?

 

[bAMtan2]

Souns s like a bug, could be the BIOS fault. Doesn't matter what the utilities say as long as your software works

 

[artbird309]

One thing you might want to try is after changing the setting in the bios to turn off the computer and unplug it for 10 seconds. I know with VT-D especially you have to do this or it will not be enabled till you do so.

 

[Eulogy]

One thing you might want to try is after changing the setting in the bios to turn off the computer and unplug it for 10 seconds. I know with VT-D especially you have to do this or it will not be enabled till you do so.

No need to unplug/hard power down. Every server I've used that I had to flip that switch on, a simple reboot was all that was necessary.

 

[RADRaze2KX]

iirc this happens because when the virtualization technology is turned on, your host OS is running as a hyper-v itself. This causes coreinfo to report that it should be run outside of a virtualized environment. If you go into the BIOS and turn off the virtualization settinsg, the OS is no longer running in hyper-v mode, and coreinfo will then report the actual settings of your processor. This also happens to me in Server 2012. All the searching I did pointed me to the above.