Whoda thunk that enabling the 64bit VT chip to enable either a 64bit guest or Windows 7 XP mode would mean that you needed to go into the security settings of the bios.


www.grc.com/securable said it would support the HyperV technology, but it wasn’t kicking in.  I knew it was in the bios, but couldn’t figure out where the VT ON switch was until I searched on the HP site.

3 Thoughts on “Whoda thunk it’s in security settings

  1. On the flipside, if you bios has Hyper threading available, you should disable it you are going to be doing Hyper-V as Hyper threading actually makes Virtual Machines less efficient.

  2. Joe Raby on November 17, 2009 at 7:37 am said:

    I’ve had a number of those Acer monitors come through my doors. And then the same ones would come back again, and again.

    I sold probably 10 of those series (I can tell by the layout of the buttons along the bottom), and Acer had some kind of major overheating problem with them where the electronics would overheat and burn out. A customer even said that theirs “blew up”, meaning there was a loud pop and a good spark that lit up the inside back of it.

    I had read before about somebody else (another reseller) that bought theirs at about the same time, had ordered 25 or so for a hospital, and they sent the whole lot of them back because of the same issue.

    I won’t carry Acer monitors anymore.

    I’ve pretty much just switched to ASUS, but I also still carry Viewsonic for those that are willing to pay for the brand.

  3. Joe Raby on November 17, 2009 at 7:46 am said:

    That is not an issue. Hyperthreading SHOULD be enabled, because it will help aid in offloading threads to each “virtual” core. This was an issue in early builds of Virtual Server 2005, but is no longer the case.

Post Navigation