3 ms·
I have no idea why option to disable it even exists in BIOSes, let alone is often set to default. Anyone have insight on it ? What's the utility of being able
by ilyt 4y ago
I have no idea why option to disable it even exists in BIOSes, let alone is often set to default.
Anyone have insight on it ? What's the utility of being able to disable virtualization ?
Even in case of "corpo disallows it" (for whatever idiotic reason) it can be turned off one way or another in OS...
- whatwherewhy 4y ago> Even in case of "corpo disallows it" (for whatever idiotic reason) it can be turned off one way or another in OS... Corpo can disallow that too via central policies
- adastra22 4y agoWell I consider this an idiotic but pragmatic reason: I've encountered laptops where Windows Subsystem for Linux will cause windows to bluescreen on boot (do they still call it that?) when VT-x is enabled. There's an open bug report tracking the on WSL for a couple of years now.
- ChuckNorris89 4y agoIIRC hardware CPU virtualization enabled in BIOS could have some negative impact/bugs on some SW, and also open the SW to some security vulnerabilities so it's a good idea to give the user the option to disable it and use SW virtualization instead.
- sumtechguy 4y agoAnother reason is market segmentation. This model has xyz, but for 50 more you can have one that does this cool thing. Even though the hardware is there. Pretty much all of the large OEM's do this. In the micro economics world it is called 'perfect pricing'. Basically segmenting your product enough and putting the prices at the right spot so everyone wants to buy along curve. In practice it is harder to do than that. So you get weird bits of hardware that can do things but are fused out. Car manufactures are trying to do this with 'rent your heated seats' kind of things. On the back end it simplifies what you buy into your pipeline and you control it with software.
- rb12345 4y agoIt's true that Blue Pill and friends were an issue 15 years ago. I would have expected VT-x to be on by default now though given that Windows 10 and 11 both use virtualisation for various security features (Credential Guard, HVCI and so on). There's no advantage to disabling it... (Edit: of course, that wasn't the case when this particular article and BIOS was written.)
- sebow 4y agoIn some cases virtualization can affect performance. Mind you last time I checked this to be the case was around 2017-2018. I don't know about the situation right now (though I wouldn't be surprised if it would still apply in some workloads).
- q-big 4y ago> What's the utility of being able to disable virtualization ? I consider the option to disable (or rather: enable this function manually if you need it) virtualization to be quite useful because if this feature is disabled, malicious software cannot install a virtualization rootkit, i.e. a rootkit that makes itself a hypervisor and moves the current OS instance into a virtual machine running under this hypervisor. See for example https://en.wikipedia.org/wiki/Blue_Pill_(software) https://en.wikipedia.org/wiki/Blue_Pill_(software)
- justsomehnguy 4y agoBecause Average Joe doesn't use virtualization at all, while Average Malicious Hacker would use it in a heartbeat if he can.
- oneplane 4y agoMarket segmentation to make more money (it needs to be configurable to lock if 'off'), and configurable with default 'off': older platforms and software was really bad at dealing with virtualisation. Only years after the likes of the Q35 and Q45 chipsets did it get better. It was so bad that up to a point you were better off disabling it and using paravirtualisation instead. The same happened during the Vt-d introduction btw.
- userbinator 4y agoolder platforms and software was really bad at dealing with virtualisation As far as I know, it just enables a few new CPU instructions, but older software that didn't know about them wouldn't use them anyway?
- oneplane 4y agoIt's not using vs. not-using, but software compiled at a time where the Vt-x and Vt-d quirks were not known causing all sorts of crashes and intermittent freezes. So for 'broken' software (and there was a lot of it - even back in the day of the turbo button) it often can be better to just not allow the software to see/use all the hardware. Example of the weird stuff you have to first know about, then detect and then mitigate, on a per-device basis: https://marc.info/?l=linux-iommu&m=139305749014927&w=2 https://marc.info/?l=linux-iommu&m=139305749014927&w=2 and that's something that when you don't do it, the software doesn't deal with it very well. Since not all software can be influenced by its operator (be it lack of skill, resources or simply legally not allowed), it can be much easier to just have a switch in the firmware where you can hide it from the software. Switching code paths based on MSR is something that is one of the safest (and broadest) things you can do early on when you start up, so in a way, such a switch is merely "supplying configuration" but in a pre-boot fashion.
- userbinator 4y agoThat example seems to be about IOMMU, which is also something that software needs to know about in order to use. I guess you were actually referring to features which the software knows about, but have errata? As another datapoint, I have a machine with VT-x enabled and Windows 98 runs fine. It just doesn't know about the extra features the CPU has (like it also doesn't know about it having more than one core).