A VM that can get around Windows 11's hypervisor and VT security nonsense?
-
Maybe you can find something here: desktop-virtualization-solutions[^]
I was hoping to avoid installing and uninstalling each of these in turn until I found one that worked, which is why I was looking for a specific one that specifically solved this problem, specifically.
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.
-
Quote:
Alternatively I'd take a way to fix the line endings
"In testa che avete, Signor di Ceprano?" -- Rigoletto
Yeah, I should have clarified that I need to be very careful about using such a tool over the existing source tree, because I don't know everything it contains. (it's a monstrous labyrinth) I can use it with a single file, but I'm also concerned Git may be trying to "fix" it for me.
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.
Did you try telling git how you want your line endings handled? Git - Git Configuration[^] Without the --global flag, you can specify it per repo. It is not WSL that is doing anything with newlines - it is VSCode and/or git itself, so this is where you should search for solutions. I would also clone on the Linux file system, not the mounted Windows drives to avoid issues with casing. If you have WSL2 on Win11 you can easily run Linux graphical git clients as well - just apt get one and fire of the command line - the UI will open without any configuration work needed. Running a VM in 2022 sounds like a very complicated solution to a simple problem.
-
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 used VM Ware player and even the payed version for long time, until some years ago it became slower and slower. Then I tried Oracle VirtualBox and I never want to go back again to VMware. The performance difference is really big, the only downside I found in VirtualBox (when running on linux mint) is that copy/paste between the VM and the host often does not works, I made a shared folder to get around that.
-
Did you try telling git how you want your line endings handled? Git - Git Configuration[^] Without the --global flag, you can specify it per repo. It is not WSL that is doing anything with newlines - it is VSCode and/or git itself, so this is where you should search for solutions. I would also clone on the Linux file system, not the mounted Windows drives to avoid issues with casing. If you have WSL2 on Win11 you can easily run Linux graphical git clients as well - just apt get one and fire of the command line - the UI will open without any configuration work needed. Running a VM in 2022 sounds like a very complicated solution to a simple problem.
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.
-
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.
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.
-
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.
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[^]
-
Did you try telling git how you want your line endings handled? Git - Git Configuration[^] Without the --global flag, you can specify it per repo. It is not WSL that is doing anything with newlines - it is VSCode and/or git itself, so this is where you should search for solutions. I would also clone on the Linux file system, not the mounted Windows drives to avoid issues with casing. If you have WSL2 on Win11 you can easily run Linux graphical git clients as well - just apt get one and fire of the command line - the UI will open without any configuration work needed. Running a VM in 2022 sounds like a very complicated solution to a simple problem.
lmoelleb wrote:
Running a VM in 2022 sounds like a very complicated solution to a simple problem.
Looks like you haven't had to use several different versions of software that are incompatible to each other just because each customer has bought something some time ago and don't want to update to "something simple"... Or have to run old software that Versions above windows 8 don't accept because "it is too old and / or too inefficient or just not compatible / supported anymore" Using VMs is actually one of the simplest solutions to solve a lot of problems.
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
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.
-
lmoelleb wrote:
Running a VM in 2022 sounds like a very complicated solution to a simple problem.
Looks like you haven't had to use several different versions of software that are incompatible to each other just because each customer has bought something some time ago and don't want to update to "something simple"... Or have to run old software that Versions above windows 8 don't accept because "it is too old and / or too inefficient or just not compatible / supported anymore" Using VMs is actually one of the simplest solutions to solve a lot of problems.
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
When I wrote "a simple problem" I was referring to the problem in the post I responded to, not every problem under the sun. And I also added the 2022 qualifier as running a VM for Linux development was a very reasonable thing to do before WSL2 (and to some degree WSL1 but that is a detail level there is no need to get into).
-
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.