A VM that can get around Windows 11's hypervisor and VT security nonsense?
-
Hey thanks! I thought that might be where the source of my trouble was coming from, but I had no idea, and I wasn't sure how I would readily check without potentially causing issues checking in to my current pull request on this project. I have had issues running scripts as well, but maybe that's because it's the terminal inside VS Code.
To err is human. Fortune favors the monsters.
You can always experiment with a local branch. Git can't perform any transformation to the files between local branches and remotes (as identity is based on SHA1 - or is it already SHA256?), so any unwanted change will be done as part of the commit into your local repo. Looking at file stamps you can easily find your new files in the .git folder and inspect them binary to see the newlines are as you want. Notice there will also be files for the folder structure and the commit, so experiment with a file at the top level to make it easy to find it.
-
Just shut down the VM and then add the following line to your .vmx file: `ulm.disableMitigations = "TRUE"` That should fix it.
Paul Sanders. If I had more time, I would have written a shorter letter - Blaise Pascal. Some of my best work is in the undo buffer.
Thank you! I'm trying it now. :)
To err is human. Fortune favors the monsters.
-
It's not security nonsense, it's having 2 active hypervisors competing for the same resource. It simply can't be done. The Windows hypervisor can now be considered part of the OS. So you have 2 options: - disable the Windows Hypervisor (it's a Windows Feature) and use a different one. - use the Windows Hypervisor I recommend using the hypervisor. It's a good implementation, don't be so fussy. Take a look here if you want the first option: Disable Hyper-V to run virtualization software - Windows Client | Microsoft Learn[^]
Frankly, anything that gets between me and what I need to do is nonsense as far as I'm concerned, even if it means a "new feature" of Windows I don't intend to use. We all have our standards. That one is mine. Adding: I don't have time to just install operating systems. I have things I need to do. I'm not switching VMs and setting up a new dev environment just to use yet another VM :~ X| . I've had this VM through several windows installs now. Anyway, another commenter showed me how to make VMWare Player go properly under Win11
To err is human. Fortune favors the monsters.
-
Frankly, anything that gets between me and what I need to do is nonsense as far as I'm concerned, even if it means a "new feature" of Windows I don't intend to use. We all have our standards. That one is mine. Adding: I don't have time to just install operating systems. I have things I need to do. I'm not switching VMs and setting up a new dev environment just to use yet another VM :~ X| . I've had this VM through several windows installs now. Anyway, another commenter showed me how to make VMWare Player go properly under Win11
To err is human. Fortune favors the monsters.
-
I've been using linux within VMWare Player because WSL is still using Windows line endings when I try to check in my source (using VS Code w/ Github) The trouble is it's so slow I want to get out and push. It says something about Windows preventing it from using the virtualization acceleration stuff, and that I need to go to advanced settings and enable some feature but VMWare Player doesn't have an Advanced tab - I think the message is for the paid version and they just didn't change it for the free one. Before I go and try any and all VMs out there, has anyone run into this issue and found a VM they can use that doesn't suffer this problem? Thanks in advance. Alternatively I'd take a way to fix the line endings and use WSL but I'm afraid anything I do will impact everything with VS Code, which I also use for local Windows coding.
To err is human. Fortune favors the monsters.
Are you sure it's not telling you that you need to go into your computer's BIOS settings and enable the virtualization settings? It'll either be called "Intel Virtualization Technology" or VTT or VT-x or whatever AMD's equivalent is (AMD-V). Also enable VT-d and IOMMU is those are in there as well. Without those, things move a lot slower.
-
Just shut down the VM and then add the following line to your .vmx file: `ulm.disableMitigations = "TRUE"` That should fix it.
Paul Sanders. If I had more time, I would have written a shorter letter - Blaise Pascal. Some of my best work is in the undo buffer.
-
Are you sure it's not telling you that you need to go into your computer's BIOS settings and enable the virtualization settings? It'll either be called "Intel Virtualization Technology" or VTT or VT-x or whatever AMD's equivalent is (AMD-V). Also enable VT-d and IOMMU is those are in there as well. Without those, things move a lot slower.
It's enabled.
To err is human. Fortune favors the monsters.
-
I've been using linux within VMWare Player because WSL is still using Windows line endings when I try to check in my source (using VS Code w/ Github) The trouble is it's so slow I want to get out and push. It says something about Windows preventing it from using the virtualization acceleration stuff, and that I need to go to advanced settings and enable some feature but VMWare Player doesn't have an Advanced tab - I think the message is for the paid version and they just didn't change it for the free one. Before I go and try any and all VMs out there, has anyone run into this issue and found a VM they can use that doesn't suffer this problem? Thanks in advance. Alternatively I'd take a way to fix the line endings and use WSL but I'm afraid anything I do will impact everything with VS Code, which I also use for local Windows coding.
To err is human. Fortune favors the monsters.
I think the problem is that Win 11 has a version of Hyper-V running under the hood, which conflicts with VMWare. Take a look at this link for how to select the virtualization system that Windows will use - Enable virtualization on Windows 11 PCs[^]
-
Just tried that config change and it was amazing the difference it made in startup and performance. Thanks for sharing that!
Yes, so was I when I first discovered it.
Paul Sanders. If I had more time, I would have written a shorter letter - Blaise Pascal. Some of my best work is in the undo buffer.
-
I've been using linux within VMWare Player because WSL is still using Windows line endings when I try to check in my source (using VS Code w/ Github) The trouble is it's so slow I want to get out and push. It says something about Windows preventing it from using the virtualization acceleration stuff, and that I need to go to advanced settings and enable some feature but VMWare Player doesn't have an Advanced tab - I think the message is for the paid version and they just didn't change it for the free one. Before I go and try any and all VMs out there, has anyone run into this issue and found a VM they can use that doesn't suffer this problem? Thanks in advance. Alternatively I'd take a way to fix the line endings and use WSL but I'm afraid anything I do will impact everything with VS Code, which I also use for local Windows coding.
To err is human. Fortune favors the monsters.
You can set git to use the line endings of your choice. I have git set to use '\n' all the time on all platforms. I set "text eol=lf" ref: href="https://docs.github.com/en/get-started/getting-started-with-git/configuring-git-to-handle-line-endings
-
That was the next one I was going to try, but I've had problems with it capturing USB devices reliably which is why I switched to VMWare Player. However, I don't need that feature for what I am currently doing so it's no big deal. Thanks. :)
To err is human. Fortune favors the monsters.
You can generally fix VirtualBox issues with USB devices by one of two options: 1) Applying a fixed capture rule - you can tell VirtualBox to always capture a specific USB ID whenever it is physically connected. Helps especially with composite devices; 2) Changing the USB controller type from USB2 to USB3, or vice versa. Some devices perform better with the USB3 controller code, other with the USB2. YMMV. Other than that, I've been using VirtualBox for development tasks with Linux guests for quite a long time and it's mostly flawless now. Except drag and drop - that thing's a pain in the kernel. But you can easily live without it anyway.
Luca The Price of Freedom is Eternal Vigilance. -- Wing Commander IV En Það Besta Sem Guð Hefur Skapað, Er Nýr Dagur. (But the best thing God has created, is a New Day.) -- Sigur Ròs - Viðrar vel til loftárása
-
I've been using linux within VMWare Player because WSL is still using Windows line endings when I try to check in my source (using VS Code w/ Github) The trouble is it's so slow I want to get out and push. It says something about Windows preventing it from using the virtualization acceleration stuff, and that I need to go to advanced settings and enable some feature but VMWare Player doesn't have an Advanced tab - I think the message is for the paid version and they just didn't change it for the free one. Before I go and try any and all VMs out there, has anyone run into this issue and found a VM they can use that doesn't suffer this problem? Thanks in advance. Alternatively I'd take a way to fix the line endings and use WSL but I'm afraid anything I do will impact everything with VS Code, which I also use for local Windows coding.
To err is human. Fortune favors the monsters.