blocks|key|4249079|text|戴尔(和索尼等)的原因禁用英特尔-VT和AMD-V是他们不能支持它.启用这一特性将意味着它们将不得不提供对其的支持，而这主要是由于支持台的知识不足而无法做到的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4249080|这至少是索尼如何制定的。|4249081|我试着从索尼的支持人员那里打听原因，这是他们给我的唯一理由。不过，我终于能够修补我的BIOS并自己启用VT。|4249082|至于其他方面，像蓝筹股这样的东西并不完全是主流。据我所知--我经常使用虚拟化技术--启用虚拟化没有什么坏处。如果有，我真的很想知道.|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|J|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|K|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|L|8|@]|9|@]|A|$]]]|H|$]]

The reason Dell (and Sony etc.) disable Intel-VT and AMD-V is that they cannot support it. Enabling the feature would mean they would have to provide support on it, which the simply cannot do, due to insufficient knowledge at the supportdesk, mainly.

That is, at least, how Sony formulated it.

I tried prying the reason from Sony support guys and that is the only thing they would give me. I finally was able to patch my BIOS and enable VT myself, though.

As for the rest, stuff like Bluepill are not exactly mainstream. And as far as I know - and I work with virtualization stuff a lot - there is no downside to enabling it. If there is though, I would really like to know about it...

blocks|key|510987|text|一个很好的理由是安全。已知存在在操作系统和硬件之间插入恶意管理程序的黑客。这允许任何人以完全透明的方式捕获任何数据。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|entityMap^0^^$0|@$1|2|3|4|5|6|7|C|8|@]|9|@]|A|$]]]|B|$]]

One very good reason is security. There have been known hacks that insert a malicious hypervisor in between your OS and your hardware. This allows anyone to capture any data in a perfectly transparent manner.

blocks|key|511031|text|我会冒险猜测，不是所有的CPU可用的一个给定的主板和BIOS组合支持VT扩展。因此，为了兼容起见，他们在BIOS中禁用了它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|511032|时代在变化，VT正变得相当普遍。所以也许我们会看到一个变化？|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|E|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|F|8|@]|9|@]|A|$]]]|D|$]]

I would hazard a guess that not all CPUs available for a given motherboard and BIOS combination support VT extensions. So they ship it as disabled in the BIOS for the sake of compatibility.

Times are changing and VT is becoming pretty common place now. So perhaps we'll see a change?

blocks|key|511140|text|我在登记册上找到了这个：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|511141|索尼的工程师和QA人员表示：“非常担心的是，启用VT会使我们的系统受到恶意代码的攻击，而恶意代码可能会深入到PC的操作系统结构中，并使后者完全失效。”|blockquote|entityMap|0|LINK|mutability|MUTABLE|url|http://www.theregister.co.uk/2009/08/06/sony_vaio_virtualization_disabled/^0|2|3|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|F|7|R|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

I found this on <a href="http://www.theregister.co.uk/2009/08/06/sony_vaio_virtualization_disabled/" rel="nofollow noreferrer">The Register</a>:

<blockquote>
 Sony's engineers and QA people were:
 "Very concerned that enabling VT would
 expose our systems to malicious code
 that could go very deep in the
 Operating System structure of the PC
 and completely disable the latter."
</blockquote>

blocks|key|511077|text|根据您打算使用的虚拟化方法，您可能不需要启用Intel-VT和AMD支持的CPU中的硬件虚拟化功能。当您需要使用这些特性时，虚拟化方法在安装未经修改的操作系统(通常是Microsoft+)时无法工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|511078|在使用VMware时，由于VMware本身提供了所有必要的功能，因此通常没有必要添加Intel和AMD芯片组的硬件虚拟化特性，并且可能导致虚拟服务器本身的性能下降。|511079|使用Xen虚拟化，如果您打算在非特权来宾域(domU's)内运行Windows，并使用完全虚拟化而不是半虚拟化方式安装，则需要使用这些特性。在我的经验中，必须启用这些功能可以显示整体性能显著下降，甚至仍然如此，但它将允许您安装Windows。其他操作系统，如Linux、*BSD和OpenSolaris，在没有硬件虚拟化的情况下安装没有问题，并且在禁用硬件虚拟化特性时看到了更好的改进。|511080|最后，这取决于您计划采用的虚拟化路径，以及您所看到的正在安装的操作系统，这是决定是否将其禁用或继续启用它的决定因素。|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|J|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|K|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|L|8|@]|9|@]|A|$]]]|H|$]]

Depending on the virtualization method you are intending to use you may not need to enable hardware virtualization featurs in Intel-VT and AMD-V capable CPUs. When you would need to use these features is when the virtualization method is unable to work when installing unmodified operating systems, usually Microsoft Windows.

When working with VMware the hardware virtualization features added byt the Intel-VT and AMD-V chipsets are usually unnecessary as VMware provides all of the necessary features within itself and it can lead to degraded performance of the virtual server itself.

With Xen virtualization you will need to use these features if you intend to run Windows within the unprivileged guest domains (domU's) and install using full-virtualization rather than para-virtualization. In my experience having to enable these features can show a significant degradation in performance overall even still but it will allow you to install Windows. Other operating systems like Linux, *BSD and OpenSolaris I have had no problems installing without hardware virtualization and see much better improvement when the hardware virtualization features are disabled.

In the end it comes down to what virtualization path your are planning to take, and what operating systems you see being installed that can be the determining factor in whether to leave it disabled or go ahead and enable it.

blocks|key|511161|text|在戴尔服务器支持下工作过，所有支持VT的服务器在默认情况下都在bios中禁用了该功能，但是如果需要的话，很容易启用它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|511162|至于索尼--出于上述原因，他们在笔记本电脑中禁用了它。|511163|我从未见过完全禁用VT/SVM功能的服务器，以至于您无法启用它。|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|H|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|I|8|@]|9|@]|A|$]]]|F|$]]

Having worked in Dell server support, all the VT capable servers have the feature disabled in the bios by default, but it is easy to enable if you need it.

As for Sony - they have it disabled in the laptops, for the reasons stated above. 

I've never seen a server with VT/SVM capabilities disabled completely, to the point you can't enable it.

blocks|key|4249046|text|我可能落后于时代，但在很多情况下，像VMWare这样的事情实际上会使很多事情变得更慢：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4249047|VMWare关于这一主题的白皮书|offset|length|entityMap|0|LINK|mutability|MUTABLE|url|http://www.vmware.com/pdf/asplos235_adams.pdf^0|0|0|G|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@$D|O|E|P|1|Q]]|A|$]]]|F|$G|$5|H|I|J|A|$K|L]]]]

I might be behind the times, but in lots of cases with things like VMWare it actually makes a lot of things slower:

<a href="http://www.vmware.com/pdf/asplos235_adams.pdf" rel="nofollow noreferrer">VMWare White Paper on the Subject</a>

blocks|key|511096|text|正如上面提到的，这都与支持有关。离开VT会降低VT成为一个因素的支持场景的数量，使大多数尚未尝试使用虚拟化路由的客户能够更快地解决问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|511097|我注意到的一件事是，在windows+7中，在我的戴尔上启用VT时，运行xp模式beta会引起与vmware工作站的冲突。两者都希望“掌握”VT扩展，而xp模式即使在退出之后也会继续运行VPC进程，因此它不会“放手”VT。因此，当您启动vmware时，您尝试并运行的任何虚拟机都会在启动时死亡。禁用bios中的VT扩展可以防止这种情况发生，但性能明显降低。|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|E|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|F|8|@]|9|@]|A|$]]]|D|$]]

As wzzrd mentioned above, it's all to do with support. Leaving VT off lowers the number of support scenarios where VT becomes a factor, enabling quicker problem resolution for the majority of customers who haven't ventured down the virtualization route.

One thing I've noted is that in windows 7, running the xp mode beta causes conflicts with vmware workstation when VT is enabled on my dell. Both want to "get hold of" the VT extension and as xp mode leaves a VPC process running even after exiting, it doesn't "let go" of the VT. So when you fire up vmware, any virtual machine you try and run dies on startup. Disabling the VT extension in the bios prevents this from happening, but with markedly reduced performance.

blocks|key|4249024|text|我非常肯定，当您只是运行本地操作系统时，硬件辅助虚拟化没有任何开销。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4249025|我能想到的禁用HAV能力的唯一原因(实际上，我从未想过这一点)是，某些应用程序/工作负载在启用HAV时运行的情况实际上可能比在本地运行时更糟糕，例如，由于MMU中的某些开销。|4249026|我一点也不担心。|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|H|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|I|8|@]|9|@]|A|$]]]|F|$]]

I am pretty sure hardware assisted virtualization does NOT have any overhead when you're just running a native OS.

The only reason I can think of for having the ability to disable it (I've never thought about this before, actually) is that certain applications/workloads could in fact run worse when HAV is enabled than when ran natively, due to certain overhead in the MMU for instance.

I wouldn't worry about it at all.

blocks|key|4249170|text|使英特尔VT使CPU更热，我有一个桌面和膝上型电脑都有这种行为，都有库存CPU冷却器。我指的是家用电脑，但它的功能是相同的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4249171|我知道AMD-V在默认情况下是启用的，但我不知道它是否使CPU更热。|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|E|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|F|8|@]|9|@]|A|$]]]|D|$]]

Enabling Intel VT makes CPU hotter, I've had a Desktop and Laptop that have had this behaviour, both with stock CPU coolers. I'm refering to Home Computers but it's the same feature.

I know that AMD-V comes enabled by default, but I don't know if it makes CPU hotter.

blocks|key|511200|text|只需看一看惠普Proliant+DL145+G3服务器。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|511201|HP通过BIOS禁用了HyperVisor+(HV)。BIOS-M绝对值不显示启用此功能的选项。关于这个问题，唯一的答案是“这个平台不支持硬件虚拟化--结束讨论”。|511202|这是根本不可能启用HV与惠普提供的BIOS。|511203|唯一的解决办法:+Coreboot+..。那就是彻底消灭这个板上的菲尼克斯-BIOS，用其他的东西代替它.|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|J|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|K|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|L|8|@]|9|@]|A|$]]]|H|$]]

Simply have a look at Hewlett Packard Proliant DL145 G3 - Servers.

HP disabled the HyperVisor (HV) by the BIOS. The BIOS-Menue don't show an option to enable this feature. The only answer to questions regarding this problem is "this platform don't support hardware virtualisation - end of discussion"

It's simply impossible to enable HV with the HP-provided BIOS.

The only solution: Coreboot ... that is to completely wipe out the PHOENIX-BIOS from this boards and replace it with something other ...

We've had a number of servers from Dell recently, all of which have had hardware-assisted virtualization disabled in the BIOS.

As far as I know hardware-assisted virtualization is a good thing - so why would Dell disable it? Does it have a performance overhead if the machine isn't acting as a virtual machine host? Are there any security issues?

In case it's relevant to your answers we will primarily be using:

<ul>
<li>Host OS: Windows Server 2003 Enterprise R2 (32-bit)</li>
<li>Guest OS:Windows Server 2003 Enterprise R2 (32-bit)</li>
<li>VMM: Virtual Server 2005 Enterprise R2 SP1</li>
</ul>

Are there any good reasons for disabling hardware-assisted virtualization?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我们最近有许多来自戴尔的服务器，所有这些服务器都在BIOS中禁用了硬件辅助虚拟化。据我所知，硬件辅助虚拟化是一件好事，那么戴尔为什么要禁用它呢？如果机器不是虚拟机主机，那么它是否有性能开销？有安全问题吗？如果它与您的答案相关，我们将主要使用：主机操作系统: Windows 2003企业R2 (32位)客户操作系统:Windows 2003企业R2 (32位)VMM:虚拟服务器2005企业R2 SP

问禁用硬件辅助虚拟化有什么好的理由吗？
EN

硬件辅助虚拟化是一件好事，那么戴尔为什么要禁用它呢？如果机器不是虚拟机主机，那么它是否有性能开销？有安全问题吗？

回答 11

Server Fault用户

Server Fault用户

Server Fault用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问禁用硬件辅助虚拟化有什么好的理由吗？EN

硬件辅助虚拟化是一件好事，那么戴尔为什么要禁用它呢？如果机器不是虚拟机主机，那么它是否有性能开销？有安全问题吗？

回答 11

Server Fault用户

Server Fault用户

Server Fault用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问禁用硬件辅助虚拟化有什么好的理由吗？
EN