221–230 of 423 posts
Earlier quoted context omitted.
But it's not how type 2 hypervisors work, and traditionally when you used virtual machines on a desktop it was type 2.
That was long time ago, most people using VMware also use ESXi, and mainframes use type 1 as well. Just those using Virtual Box for free not.
Most people using it are also using servers. Is ESXi on desktops/workstations anything other than very niche?
Earlier quoted context omitted.
So if someone installs Linux themselves they don't meet this bar you're setting? That seems pretty far from the normal open source ethos.
Ah, so using evil commercial OSes is part of that so called ethos?
Earlier quoted context omitted.
I don't think they deprecated shared folders, only shared VMs (a function that enables Workstation to act as a virtualization server). Source: https://en.wikipedia.org/wiki/VMware_Workstation#Version_his...
That’s a shame. I have a high-powered desktop and sometimes it’s nice to work from the patio by opening a few VMs on my laptop. I get the oomph of the big box with the mobility of the laptop. To be fair, this feature always felt..rickety. But it was very nice.
You would be missing the remote power operations.
FWIW, I am working on a product called Vimarun [0] that is aimed to replace most of that missing functionality over time.
No remote power operations yet, but that will come.
Huh. I've used WSL2 and got extensively and never had any problems.
Brad Silverberg: "drdos has problems running windows today, and I assume will have more problems in the future."
Jim Allchin: "You should make sure it has problems in the future. :-)"
More: - WSL2 sometime corrupt .zsh_history and git https://github.com/microsoft/WSL/issues/5026 - WSL2 corrupts ext4 filesystem https://github.com/microsoft/WSL/issues/5895
> Feel like booting Linux on a separate disk because of these issues. It always seemed strange to me that people would rather use WSL than the real thing when Windows doesn't bring much advantage. What am I missing ?
I think calling it WSL2 was a mistake. The predecessor, WSL, "just worked" and it was more a less a linux experience for most practical purposes-- and certainly better than hoary old cygwin. This caused a lot of people to believe they could just transition to WSL2, lead on by the promise of an even more performant linux experience. The documentation didn't say anything about complications from attempting this, so a l…
Earlier quoted context omitted.
Why would VM-based WSL2 use any less RAM?
WSL VMs are gen2 (fully paravirtual) hyper-v VMs, so use dynamic memory allocation. VirtualBox, even with Hyper-V as its engine, doesn't do this. I don't think any standalone Linux distros offer a standalone Hyper-V paravirtual image that is not a WSL2 image.
I believe the "Linux Integration Services" for Hyper-V are actually mainlined at this point so I would expect most things to work. Setting up RDP for enhanced desktop sessions is the only painful thing I remember.