3 ms·
This is still with Linux running in a VM though, right? I'd like a lightweight VM for legacy Windows and Linux running on metal. Given Microsoft's zeal for leg
by mullingitover 7y ago
This is still with Linux running in a VM though, right? I'd like a lightweight VM for legacy Windows and Linux running on metal.
Given Microsoft's zeal for legacy support I'd say there's a snowball's chance in hell for this, but a man can dream.
- SteveNuts 7y agoWSL version 2 uses the Hyper-V Virtualization API but is not a VM. The first version of WSL is just another process in task manager, with all the syscalls and filesystems emulated.
- chrismorgan 7y agoWell, each WSL1 process is a Windows process. If you’re running vim in bash, for example, you’ll see “vim” and “bash” as separate processes in Task Manager. WSL is all about ELF binaries natively, just as Win32 runs PE executables natively.
- kevingadd 7y ago"windows process" is misleading, WSL uses a separate "linux subsystem" with its own syscalls, process/thread data structures, etc. It also uses its own file system (albeit with all the state stored in NTFS and affected by filter drivers, which is why its I/O is slow)
- chrismorgan 7y agoThey are Windows processes, just as the Win32 subsystem also spawns Windows processes.
- dblohm7 7y agoProbably best to refer to them as NT processes for the sake of clarity.
- chrismorgan 7y agoTrue, I thought that a few hours after I wrote my last comment but couldn’t update it by that point and didn’t respond to it. Windows NT is the kernel, Win32 is the Windows subsystem that everyone’s used to (including kernel32.dll), WSL is a subsystem that runs ELF binaries and implements the Linux syscalls. It’s not yet obvious to me how much WSL2 is actually even a Windows subsystem, given that it’s running it as an actually separate OS.
- godelski 7y agoI just want Linux with the ability to use PowerPoint. (I also want to just be about to plug in my HDMI to my laptop and have it work. Literally the only two things I care about)
- marcianx 7y agoFWIW, I have given major conference talks years back on my linux laptop with PowerPoint running via Crossover Office (wine), mostly due to my advisor's insistence on using PowerPoint. So that has already been a thing for a long while.
- godelski 7y agoMy issue is that with nvidia laptops the hdmi connection almost never works as expected, when I have cuda installed. I'll try proprietary or noveau drivers. I've driven my monitor with intel drivers. I've tried so many things, but it has been multiple laptops that I've just never gotten this to work. I just can't have cuda and use my laptop for presentations. So I just always keep a windows partition just for presentations. If you do have a suggestion I'd love to hear it. I've never used crossover. Thanks, I'll look into it.
- rightbyte 7y agoI tried to do CUDA programming on a laptop with Ubunto but gave up. It worked fine on a stationary computer. There has to be something with Cuda that messes everything up on laptops.
- giancarlostoro 7y agoI dont think its a VM like Docker no. WSL processes show up under the task manager. This is more like Wine but Line... In a sense. But a little trickier.
- monocasa 7y agoDocker's not a VM.
- dboreham 7y agoSomeone who uses MacOS might think Docker implies a VM perhaps? (Linux VM needed to get Linux Containers to run).
- fortran77 7y agoDo Docker people really think it’s a VM? Or has the meaning of “VM” shifted this past year?
- robrtsql 7y agoI think the OP is probably referring to the fact that running Docker on Windows and macOS is accomplished by running a Linux VM which the Docker containers run in. Not that Docker containers are VMs.
- fortran77 7y agoI didn't know that macOS users don't run Docker natively! On Windows, it's native: https://docs.docker.com/docker-for-windows/ https://docs.docker.com/docker-for-windows/
- mtzet 7y agoDocker desktop runs a Hyper-V VM. Prior to that, Docker used a Virtualbox VM on Windows. The current plan seems to be to integrate with WSL2 once that ships [1]. [1] https://engineering.docker.com/2019/06/docker-hearts-wsl-2/ https://engineering.docker.com/2019/06/docker-hearts-wsl-2/
- kop316 7y agoI would actually wonder if it could do that via VMs. That why you can keep compatibility, but then change the underlying system.
- tbrock 7y agoJust run Linux and then run a Windows VM in QEMU, seems like you can do this now.
- naikrovek 7y agoWhen you run a type-1 hypervisor, the only thing running on the metal is the hypervisor. This is what happens in the case of WSL 2; both Linux and Windows (the host OS) run in very (very) lightweight VMs.
- inlined 7y agoIirc, even the Win32 APIs sit above the subsystem layer. There was the OS/2 subsystem back in the day, Win32, and one more I can’t remember from my training 11 years ago.