Windows Virtualization Enabled
Dixie Schlatter
On my notification I am redirected to a Kaspersky website page where I'm told I have to enable virtualization in the BIOS. Except it's already enabled and I have checked and rechecked it. systeminfo also confirms I have it.
been there already (that is the website that a link in the antivirus notification takes you) and like I said I am 100% sure that I have it enabled it. FYI that website has no information other than how to enable it in BIOS in case it is disabled. That's why I opened this thread.
I only have Kaspersky on my Windows 11 as far as antivirus program is concerned. There is of course Microsoft's own built-in antivirus but that one is turned off automatically when Kaspersky is turned on.
Any Windows 11 feature that uses Device Guard, Windows Hyper-V enabled... or Windows SandBox enabled, I think also Linux subsystem also need Hyper-V enabled (not sure), will lead to a warning of Kaspersky own Hyper-V / Hardware virtualization protection.
That info page needs to be updated ASAP. Also in another area: the "Windows 10" subtitle is already outdated (since early last year already we have another Windows version on the market: Windows 11 so it should read "Windows 10 & 11"
Because while this core isolation problem was solved, I discovered a new problem while trying to solve that: Kaspersky conflicts with AdGuard (an anti ad protection program that I have on my computer). Specifically I had set up AdGuard to be my DNS resolver instead of the usual (Windows Settings > Network & Internet). The reason is because I don't want to change the Windows's basic DNS settings - I want that to remain "Automatic" by default so I don't get connection problems with some public networks.
So I want to continue using AdGuard. Which means I have no choice but to stop using Kaspersky Security Cloud. Because KSC has no option to "allow" me to use AdGuard HTTP / DNS protection side by side (something I can do with AdGuard + Windows Defender).
Many IT businesses have deployed servers that run only at a fraction of their total capacity. This is mostly because they dedicate their physical server to one particular application. This is not a very efficient mechanism as there is the availability of excess capacity that is going to waste. It also results in higher operating costs.
Hardware virtualization has gained popularity in server platforms. The basic idea to enable hardware virtualization is to integrate numerous small physical servers into a single large physical server for the processor to be used effectively. The Operating System that runs on the physical server is converted into an OS that runs inside the virtual machine.
It has many advantages to it. The main advantage is that it is much easier to control a virtual machine than a physical server. Operating systems running on the machine appear to have their own memory and processor. Hardware virtualization can increase the scalability of your business while also reducing expenses at the same time.
Open your task manager by using Ctrl+Shift+Esc keys. If your processor supports hardware virtualization, you will see virtualization as Enabled along with the other details, or otherwise disabled. If it does not support virtualization, you will not see Hyper-V or virtualization mentioned in the task manager.
After finding the CPU configuration section, you need to find the menu or option where it allows you to enable hardware virtualization. Hardware virtualization is enabled in the acceleration section. Depending upon your PC, look for any of these or similar names such as Hyber-V, Vanderpool, SVM, AMD-V, Intel Virtualization Technology or VT-X.
After selecting the enabling virtualization option, look for the option that allows you to save these changes. Before saving it, you may have to first exit the menu and then click the save changes option. Now you have successfully enabled hardware virtualization on your computer.
VirtualMetric offers enhanced virtualization monitoring software to ease the complexity of your virtualized environment. To get to know more about how our product works, click here by getting a free trial.
Today, I decided to upgrade from WSL 1 to WSL 2. On WSL 1, I had no issues getting both Kali Linux or Ubuntu to function on WSL 1. When upgrading to WSL 2, both Kali and Ubuntu failed to upgrade to version 2. I read that uninstalling and reinstalling them could fix this issue.However, upon reinstalling both of them, my system now fails to detect any installed distro, despite the distro's being installed. Launching both Kali or Ubuntu gives the same error.
When researching this error, and from reading the official WSL 2 install guide from Microsoft, the error always seems to be because the system doesn't have virtualization enabled in the BIOS. This is really confusing as I have checked over 4 different times if I missed any virtualization setting in my BIOS, and have verified it is all enabled. I also have confirmed I have the NX feature enabled as well. Even HWiNFO detects I have virtualization enabled:
I have also made sure that the Virtual Machine Platform, Windows Subsystem for Linux and the Windows Hypervisor Platform features are all enabled. Not only this, but I can also create and run any number of VMs from VirtualBox without any errors or issues whatsoever.
Other troubleshooting steps I have gone through was resetting the WSL service, reset my machine (multiple times), update the WSL kernel, verify my Win version is in 19041 or above, and waited 20 minutes after boot to see if I was just being impatient.
We are aware of an issue where using the DISM (Deployment ImageServicing and Management) tool to repair corruption on systems runningthe May 2020 Update does not always report the correct status. Thiswill be fixed in an upcoming servicing release.
I found the solution on GitHub, and some of the information in this answer was taken from there. It was challenging for me to find a solution, so I'm adding this information here for others who may be struggling with the same issue.
I had the same error and with the virtualization enabled too. After uncheck Windows Subsystem for Linux, Windows Hypervisor Platform and Virtual Machine Platform, restarting the pc and enable them again the error disapeared and I could install WSL 2.
you have to enable virtualisation in BIOS.There is no other way. I spent 2 hours with MS adviser on it. We done everything and ended with no success.I saw somewhere later that BIOS setting advice. It works! Virtualisation is disabled there. Once enabled Ubuntu works.
Oh! I found it. In "add / remove functionnalities", you have Hyper-V and something else about virtualization. That one was missing. I only have the french translation of this func. so giving it to you won't probably help. Look for the entire list and double-check. Actually hyper-v is not required.Debian up and running.
3600
MSI X570 (mid tier board)
Happens in Windows, Linux, Unix (BSD), etc. Happens across multiple BIOS versions (its been a multi-year standing issue).
I am scrambling to put together a second machine just to run a single appliance because of this.
Effectively, Virtualization being bugged is costing me more than this CPU did.
It didn't happen on the former R5 1600 (that I noticed).
Both of us this week turned on SVM (virtualization) to try to get some things done independently, and both of us unprompted mentioned trying to and it causing such great instability that it just wasn't viable, even for a short term task.
This is the kind of thing that makes me say: Either ya gotta replace the CPU with one that isn't bugged (this is a major manufacturing defect), or I gotta ditch AMD despite my frustrations with Intel. This type of bug costs me way too much.
If anyone has a fix for it, let me know, because as of now I'm fed up and my only solution is to say to AMD what Linus Torvalds once said to nVidia.
Everyone I know is on AMD, because I told them it was better. This makes me look bad.
I don't know if its a microcode fix, a Bios fix, or a hardware fix (replacement), but whatever it is, it needs to happen.
AMD, ya gotta make this one right, right away. It simply can't stand when so many people have turned to you for affordable workstation machines (relative to what was available prior to first gen Ryzen).
Pretty much everything in computer affect everything else too. Depending on situation, I would likely try with another software, lower memory speed, check temperatures, make sure PSU's are powerfull enough and not too old as virtualization can stress system more. Running an all-core clockspeed instead of PBO or something else might be a good idea. Make sure baseclock is 100Mhz.
EDIT2: From what I found with google, it works with most people, but someone mentioned disabling IOMMU or using a fixed clockspeed has helped - I find the latter a bit strange, but in general it can be more stable if there are any stability issues I suppose. Also there is a thread on this board from 2018 where someone mentioned you shouldn't have Ryzen master if you have virtualization enabled, but this can be on outdated thing. More interestingly, on that this thread he apparently got his machine working by reinstalling operating system while virtualization is enabled. EDIT3: And forgot a link to that thread -master-and-virtualization-cause-bsod/td-p/96928
So, running multiple operating systems. Not a software problem. Spent maybe 100 hours chasing the crashes and lockups.
Disabling IOMMU is not a fix. Its creating another, equally problematic problem that chops off half of the functionality of virtualization.
I appreciate it though - I have looked at those and tried them, but they didn't fix it for me.
I am not running *the latest* bios because others have, it didn't fix the problem, and it created some new problems for them (I am on X370, so the benefit to it is 5000 series support, which doesn't do anything for me at the moment).
The all core clockspeed thing, I may have to give that another try.
Powersupply is overspec'd by 4x based on max actual system utilization, and of high quality. And I don't let anyone I know get a cheap power supply. Some are running their ram at 2133, most at 3200 or 3600, all with the same problem.
And yeah, I agree with the baseclock thing. I never deviate on that - thats just begging for issues I don't want to chase.
I don't run ryzen master, or any specialty things for specific pieces of hardware aside from a bit of stuff for nVidia GPUs, and when necessary a USB3 driver (I don't think thats necessary anymore, to manually add that, but it was at one point).
And yeah the instability is just, locking up, or outright crashing, at random, no pattern that I can discern.