Could you please create a dedicated section for Windows 10 Bash ?

pparks1 said:

The biggest pitfall for me is going to be that WSL 2 is relying on Hyper-V. I use VirtualBox for a ton of other VM things and the two cannot co-exist without running the following commands to turn Hyper-V on and off and rebooting.

bcdedit /set hypervisorlaunchtype offbcdedit /set hypervisorlaunchtype auto

Hi there

With newer hardware the evaluation version of VMWare workstation rel 20H1 --valid until Oct 2020 --will run concurrently with HYPER-V -- VM's created under both products will run concurrently too -- so the chances are that an upcoming release of VBOX might also enable this facility.

Actually reading between the lines a bit there's nothing wrong "per se" in running Linux or any other OS as a sort of hybrid OS -- I believe QEMU / KVM works similarly --and that has no problem with VM's running concurrently with those created by VMWare (and probably Virtual box too).

The main object of all this stuff as well is to avoid having to go for full paravirtualisation options of the guest OS which then incurs the main overhead of the HOST OS -- if you can keep that bit tiny then your VM's will profit greatly.


Cheers
jimbo

jimbo45 said:

With newer hardware the evaluation version of VMWare workstation rel 20H1 --valid until Oct 2020 --will run concurrently with HYPER-V -- VM's created under both products will run concurrently too -- so the chances are that an upcoming release of VBOX might also enable this facility.

I am eagerly awaiting for interoperability between VirtualBox and Hyper-V. I used VMWare Workstation for years, and my previous employer purchased licensing for me. There is no requirement for me to use VMWare Workstation at my current job, but i like to run VM's locally for experimental testing and learning. Therefore, I am using VirtualBox without the extension pack as it's free. And I can also use it at home, with the extention pack (if I want)...as it's free.