As the talk about hardware virtualization heats up from Microsoft and others you might find yourself wondering if the current hardware you're running supports it. My HP xw9300 workstation doesn't (older AMD Opterons), but it looks like my xw8400 does (Intel Xeon 5150s).
More info on programs you can use (including the one above) found here: http://blogs.msdn.com/volkerw/archive/2007/05/21/hardware-virtualization-check-utility.aspx
Determine Virtualization Readiness in 3 Seconds
Some other tidbits of info:
If you install the Active Directory Domain Services role and use the Active Directory Domain Services Installation Wizard (dcpromo.exe) to configure that role on the same physical computer on which the Hyper-V role is installed, you will receive a STOP error message 7B on the physical computer when you try to start a virtual machine.
To avoid this issue, do not install Active Directory Domain Services and Hyper-V on the same physical computer.
Microsoft Hyper-V site to find out more info if you like.
Update: Looks like AMD has released a tool help out here: http://blogs.msdn.com/virtual_pc_guy/archive/2008/03/31/amd-releases-hyper-v-check-tool.aspx
Hyper-V対応チェックツール(SecurAble)
My 8-way Opteron server running Hyper-V shows "No" for hardware virtualization support... sigh maybe someone will come out with a better tool to scan for capable machines at some point. :-)
We also have xw8400's, ours have 2 Xeon X5355 Processors in each of them. I have updated the BIOS and enabled Intel-VT and DEP support but Hyper-V still give me the "unable to change state" error. What BIOS option did you enable/disable to get your xw8400 to work?
Wes
Hey Wes, I enabled DEP and Virtualization under “OS Security” in the BIOS.
Hyper-V is probably one of the more exciting technologies to come out of Redmond, on the IT Pro side
Running the securable app from within and virtual environment, meaning, on a MS Hyper-V or ESX 3.5 guest OS, I get NO to hardware virtualization.
Is this normal? What does this indicate?
Hi MC, yes this would be normal if you ran it inside a VM. A VM cannot virtualize another guest.