I don't use virtualbox, so I'm guessing at some features: * The Linux filesystem shows up in Windows as a disk even when the underlying VM is not booted, you c

I don't use virtualbox, so I'm guessing at some features: * The Linux filesystem shows up in Windows as a disk even when the underlying VM is not booted, you can see an example here: https://redmondmag.com/articles/2020/04/08/~/media/ECG/redmondmag/Images/2020/04/0408red_Subsystem_b.ashx https://redmondmag.com/articles/2020/04/08/~/media/ECG/redmo... * And for me the nice one is the integration with VS Code, I just select which distro I want to work in and VS Code will start it (if it isn't running), connect to it as a remote dev environment, and be able to control it as if the VM were within VS Code. It can be done manually with VirtualBox, but VirtualBox gives me no advantages in return. * The networking implementation makes both 127.0.0.1 which is occasionally useful for me.