4 ms·
After upgrading to WSL2, I started having issues with a Virtualbox VM. Turns out it didn't play nicely with HyperV. I went back to WSL1.
by dehrmann 6y ago
After upgrading to WSL2, I started having issues with a Virtualbox VM. Turns out it didn't play nicely with HyperV. I went back to WSL1.
- uncledave 6y agoThat’s because HyperV is a type 1 hypervisor and vbox is a type 2 hypervisor. They don’t mix well :) Best option is still vbox and putty IMHO. VScode will work with it and SSH fine. Or say fuck it, buy a Mac and do all your Linux work in the cloud.
- noisem4ker 6y agoNewer VirtualBox releases can run virtual machines on top of Hyper-V as a virtualization engine. It is slower than VirtualBox' own engine, but overall it is still a better experience than Hyper-V Manager.