Are there any disadvantages to enabling Intel hardware virtualization in BIOS settings?
I'm new to developing apps in React Native and in order to get the Android emulator to work I had to enable Intel hardware virtualization/VT-X in the BIOS settings.
I'm a web developer so I was a bit nervous about touching the BIOS settings at first because I haven't done anything in the BIOS settings before, but I did it anyway following the advice given from this site.
I just wanted to ask, are there any disadvantages to keeping hardware virtualization enabled? Is there any damage to hardware if left on? Or should it only be enabled when needed? Sorry if this seems like a silly question.
Thanks!
react-native
android-emulator virtualization bios asked Nov 16 '18 at 14:28
danny471danny471
112
add a comment |
I'm new to developing apps in React Native and in order to get the Android emulator to work I had to enable Intel hardware virtualization/VT-X in the BIOS settings.
I'm a web developer so I was a bit nervous about touching the BIOS settings at first because I haven't done anything in the BIOS settings before, but I did it anyway following the advice given from this site.
I just wanted to ask, are there any disadvantages to keeping hardware virtualization enabled? Is there any damage to hardware if left on? Or should it only be enabled when needed? Sorry if this seems like a silly question.
Thanks!
react-native
android-emulator virtualization bios asked Nov 16 '18 at 14:28
danny471danny471
112
1
This may be of some use: serverfault.com/questions/390012/…
– Michael Petch
Nov 20 '18 at 2:18
add a comment |
I'm new to developing apps in React Native and in order to get the Android emulator to work I had to enable Intel hardware virtualization/VT-X in the BIOS settings.
I'm a web developer so I was a bit nervous about touching the BIOS settings at first because I haven't done anything in the BIOS settings before, but I did it anyway following the advice given from this site.
I just wanted to ask, are there any disadvantages to keeping hardware virtualization enabled? Is there any damage to hardware if left on? Or should it only be enabled when needed? Sorry if this seems like a silly question.
Thanks!
react-native
android-emulator virtualization bios asked Nov 16 '18 at 14:28
danny471danny471
112
I'm new to developing apps in React Native and in order to get the Android emulator to work I had to enable Intel hardware virtualization/VT-X in the BIOS settings.
I'm a web developer so I was a bit nervous about touching the BIOS settings at first because I haven't done anything in the BIOS settings before, but I did it anyway following the advice given from this site.
I just wanted to ask, are there any disadvantages to keeping hardware virtualization enabled? Is there any damage to hardware if left on? Or should it only be enabled when needed? Sorry if this seems like a silly question.
Thanks!
react-native
android-emulator virtualization bios react-native
android-emulator virtualization bios asked Nov 16 '18 at 14:28
danny471danny471
112
asked Nov 16 '18 at 14:28
danny471danny471
112
asked Nov 16 '18 at 14:28
danny471danny471
112
asked Nov 16 '18 at 14:28
danny471danny471
112
asked Nov 16 '18 at 14:28
danny471danny471
112
112
1
This may be of some use: serverfault.com/questions/390012/…
– Michael Petch
Nov 20 '18 at 2:18
add a comment |
1
This may be of some use: serverfault.com/questions/390012/…
– Michael Petch
Nov 20 '18 at 2:18
1
1
This may be of some use: serverfault.com/questions/390012/…
– Michael Petch
Nov 20 '18 at 2:18
This may be of some use: serverfault.com/questions/390012/…
– Michael Petch
Nov 20 '18 at 2:18
add a comment |
2 Answers
2
active
oldest
votes
Every feature in the platform has the possibility of providing a means for malware to gain control. I’m not aware that VMX is susceptible, but it seems like a reasonable precaution to leave disabled features that you don’t need.
If you need it occasionally, it is perfectly reasonable to leave it enabled all the time. There is no harm to the hardware nor any additional power usage or performance impact in having it enabled in the BIOS but not being used. I think this would be safer than changing it in the BIOS every time it is needed.
However some operating systems may automatically make use of it if is available. They would do this specifically to reduce the risk of malware and contain the impact of bugs in the system. In this case, there may be some additional power usage and performance impact, to obtain the benefit.
answered Nov 20 '18 at 0:11
prlprl
4,7191316
add a comment |
There was an attack in around 2006 called blue pill, that used virtualization to create the so called virtualized rootkit, a rootkit that should be undetectable.By virtualizating the target os while hiding itself The attack spanwed countermeasure by bios manufacturers, that disabled the virtualization extension by default.
There was no virtualized rootkit found in the wild, and the attack proved to be detectble ( timing attacks, and other holes in the virtualization). The attack lost of its relevance and today the BIOS settings represent the panic that surrendered blue pill. If an attacker would gain ring zero acssses that would allow him to create a virtualized rootkit, most of the chance he wouldn't create it, and if he would it would not be much scarier then a regular kennel rootkit.
answered Dec 2 '18 at 0:48
dmgdmg
233
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53339792%2fare-there-any-disadvantages-to-enabling-intel-hardware-virtualization-in-bios-se%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Every feature in the platform has the possibility of providing a means for malware to gain control. I’m not aware that VMX is susceptible, but it seems like a reasonable precaution to leave disabled features that you don’t need.
If you need it occasionally, it is perfectly reasonable to leave it enabled all the time. There is no harm to the hardware nor any additional power usage or performance impact in having it enabled in the BIOS but not being used. I think this would be safer than changing it in the BIOS every time it is needed.
However some operating systems may automatically make use of it if is available. They would do this specifically to reduce the risk of malware and contain the impact of bugs in the system. In this case, there may be some additional power usage and performance impact, to obtain the benefit.
answered Nov 20 '18 at 0:11
prlprl
4,7191316
add a comment |
Every feature in the platform has the possibility of providing a means for malware to gain control. I’m not aware that VMX is susceptible, but it seems like a reasonable precaution to leave disabled features that you don’t need.
If you need it occasionally, it is perfectly reasonable to leave it enabled all the time. There is no harm to the hardware nor any additional power usage or performance impact in having it enabled in the BIOS but not being used. I think this would be safer than changing it in the BIOS every time it is needed.
However some operating systems may automatically make use of it if is available. They would do this specifically to reduce the risk of malware and contain the impact of bugs in the system. In this case, there may be some additional power usage and performance impact, to obtain the benefit.
answered Nov 20 '18 at 0:11
prlprl
4,7191316
add a comment |
Every feature in the platform has the possibility of providing a means for malware to gain control. I’m not aware that VMX is susceptible, but it seems like a reasonable precaution to leave disabled features that you don’t need.
If you need it occasionally, it is perfectly reasonable to leave it enabled all the time. There is no harm to the hardware nor any additional power usage or performance impact in having it enabled in the BIOS but not being used. I think this would be safer than changing it in the BIOS every time it is needed.
However some operating systems may automatically make use of it if is available. They would do this specifically to reduce the risk of malware and contain the impact of bugs in the system. In this case, there may be some additional power usage and performance impact, to obtain the benefit.
answered Nov 20 '18 at 0:11
prlprl
4,7191316
Every feature in the platform has the possibility of providing a means for malware to gain control. I’m not aware that VMX is susceptible, but it seems like a reasonable precaution to leave disabled features that you don’t need.
If you need it occasionally, it is perfectly reasonable to leave it enabled all the time. There is no harm to the hardware nor any additional power usage or performance impact in having it enabled in the BIOS but not being used. I think this would be safer than changing it in the BIOS every time it is needed.
However some operating systems may automatically make use of it if is available. They would do this specifically to reduce the risk of malware and contain the impact of bugs in the system. In this case, there may be some additional power usage and performance impact, to obtain the benefit.
answered Nov 20 '18 at 0:11
prlprl
4,7191316
answered Nov 20 '18 at 0:11
prlprl
4,7191316
answered Nov 20 '18 at 0:11
prlprl
4,7191316
answered Nov 20 '18 at 0:11
prlprl
4,7191316
4,7191316
add a comment |
add a comment |
There was an attack in around 2006 called blue pill, that used virtualization to create the so called virtualized rootkit, a rootkit that should be undetectable.By virtualizating the target os while hiding itself The attack spanwed countermeasure by bios manufacturers, that disabled the virtualization extension by default.
There was no virtualized rootkit found in the wild, and the attack proved to be detectble ( timing attacks, and other holes in the virtualization). The attack lost of its relevance and today the BIOS settings represent the panic that surrendered blue pill. If an attacker would gain ring zero acssses that would allow him to create a virtualized rootkit, most of the chance he wouldn't create it, and if he would it would not be much scarier then a regular kennel rootkit.
answered Dec 2 '18 at 0:48
dmgdmg
233
add a comment |
There was an attack in around 2006 called blue pill, that used virtualization to create the so called virtualized rootkit, a rootkit that should be undetectable.By virtualizating the target os while hiding itself The attack spanwed countermeasure by bios manufacturers, that disabled the virtualization extension by default.
There was no virtualized rootkit found in the wild, and the attack proved to be detectble ( timing attacks, and other holes in the virtualization). The attack lost of its relevance and today the BIOS settings represent the panic that surrendered blue pill. If an attacker would gain ring zero acssses that would allow him to create a virtualized rootkit, most of the chance he wouldn't create it, and if he would it would not be much scarier then a regular kennel rootkit.
answered Dec 2 '18 at 0:48
dmgdmg
233
add a comment |
There was an attack in around 2006 called blue pill, that used virtualization to create the so called virtualized rootkit, a rootkit that should be undetectable.By virtualizating the target os while hiding itself The attack spanwed countermeasure by bios manufacturers, that disabled the virtualization extension by default.
There was no virtualized rootkit found in the wild, and the attack proved to be detectble ( timing attacks, and other holes in the virtualization). The attack lost of its relevance and today the BIOS settings represent the panic that surrendered blue pill. If an attacker would gain ring zero acssses that would allow him to create a virtualized rootkit, most of the chance he wouldn't create it, and if he would it would not be much scarier then a regular kennel rootkit.
answered Dec 2 '18 at 0:48
dmgdmg
233
There was an attack in around 2006 called blue pill, that used virtualization to create the so called virtualized rootkit, a rootkit that should be undetectable.By virtualizating the target os while hiding itself The attack spanwed countermeasure by bios manufacturers, that disabled the virtualization extension by default.
There was no virtualized rootkit found in the wild, and the attack proved to be detectble ( timing attacks, and other holes in the virtualization). The attack lost of its relevance and today the BIOS settings represent the panic that surrendered blue pill. If an attacker would gain ring zero acssses that would allow him to create a virtualized rootkit, most of the chance he wouldn't create it, and if he would it would not be much scarier then a regular kennel rootkit.
answered Dec 2 '18 at 0:48
dmgdmg
233
answered Dec 2 '18 at 0:48
dmgdmg
233
answered Dec 2 '18 at 0:48
dmgdmg
233
answered Dec 2 '18 at 0:48
dmgdmg
233
233
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53339792%2fare-there-any-disadvantages-to-enabling-intel-hardware-virtualization-in-bios-se%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
This may be of some use: serverfault.com/questions/390012/…
– Michael Petch
Nov 20 '18 at 2:18