Linked by Thom Holwerda on Fri 23rd Sep 2011 22:22 UTC, submitted by kragil
Permalink for comment 490640
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
More News »
Sponsored Links



Member since:
2006-01-14
And some manufacturers have already stated that the option to disable will not be present. Many OEM's even now with just a regular BIOS do not allow users to change all the features that are present. Dell is pretty good, but that doesn't mean the option will always be there. Also, if Microsoft can mandate that OEMs include this functionality, what is to stop Microsoft from later mandating that the disable option be removed?
Case in point, I have a 1U server that has procs that include VT-x. The motherboard has a chipset that supports VT-x. The OEM set the BIOS to permanently disable hardware virtualization. Why? Because they could I guess? Because it was sold at a price point that they didn't want hurting sales of more robust expensive servers?