![]() ![]() * Btw, you also get a (small, but non-zero) performance hit on your Windows box by using WSL, even when it is not running, since now Hyper-V is what boots your system as the ring-0 guy. Doesn't hijacks your Virtualization extensions, like with WSL, which need Hyper-V which actually boots your computer with a Hyper-V hypervisor and blocks nested virtualization, meaning, you can't use other virtualization technologies properly outside of Hyper-V if you use WSL* No need to 'service docker start' on every WSL run Services run automatically, as it's just a normal Linux install. Just use "Remote - SSH" and connect to your VM and keep your local lower input lag - Works just the same as "Remote - WSL" as both essentially use the same mechanism - a remote connection to a Linux server. With VSCode, you don't even need a X server. With VcXsrv or Xorg on Cygwin, you'll get graphical apps just the same, and with the virtio-net network card on the VM (instead of Virtualbox's default Intel Pro1000 - my protip :D) you'll get enough speed to watch youtube on google chrome - e.g.: More than sufficient speed for using an IDE like P圜harm etc Real VM you can snapshot and transfer to another computer running VirtualBox, even on another OS, as VBox supports other operating systems. Honestly, WSL has got nothing over a VirtualBox VM using a virtio-net network device on it. The WSLg system seems really nice for any software I might run that doesn't support remote hosts.įor me, it's all upsides and no real downsides to just running WSL. " in the WSL term and having it just launch VSCode in Windows and be connected. There is a level of integration that is pretty nice. I can still run multiple VMs if I need to with Hyper-V. Both seem to work fast and I don't have to do anything with them. I like the default drive and network sharing. ![]() This is really nice in general but particularly on laptops with less RAM. It supports dynamic memory allocation and in the new 2.0 release I believe it can free memory. The WSL vm feels much more performant to me. I haven't needed to restart docker after booting WSL. VirtualBox still works if I need to access something off my old VMs, it's just dog slow for some reason using Hyper-V on my system. There are other benefits to me and I'm not missing anything by moving to WSL. I'm a Pycharm user (and Pycharm unfortunately has meager support for remote, where VSCode shines) and I use it graphically like this - there's still some input lag tho, but it's quick enough for me. With the virtio-net device, even remote X11 becomes a real possibility with windows apps like VcXsrv. ![]() Much better performance since it's essentially a virtual device with unbounded speed. One tip that I have is: Set a secondary NIC in your VirtualBox VM to a 'host only network' and use 'virtio-net' instead of the default emulated Intel Pro1000 cards. Try it out (VSCode+Remote SSH to Vbox), you'll enjoy just the same as VSCode+WSL Easier to image/snapshot/transfer to another box or even another operating system, as VirtualBox runs in other OSes.Īnd you get the same native VSCode experience. No need to "service docker start" on every WSL boot. Services run normally, since it's a normal linux box. In fact, when you enable WSL/Hyper-V, your windows itself boots as a kind-of-VM from a Hyper-V root, so WSL is just an additional VM inside that cage. I don't need to enable Hyper-V, which hijacks virtualization and disables other softwares (like VirtualBox) from using it. I still use the virtualbox setup because I feel it has advantages compared to WSL: VSCode remote also works equally well via "remote SSH" to your VirtualBox Setup.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |