The other thing you need to have in order to get started is the Ubuntu 20.04 install image.
Windows users and others that aren’t running Ubuntu, you can head over to and download the latest version of VirtualBox for your system. If not, we have a guide about how to install VirtualBox on Ubuntu 20.04 Focal Fossa that you can follow before meeting back here.
This tutorial assumes that you already have VirtualBox installed. $ – requires given linux commands to be executed as a regular non-privileged user # – requires given linux commands to be executed with root privileges either directly as a root user or by use of sudo command Privileged access to your Linux system as root or via the sudo command. Installed Ubuntu 20.04 or upgraded Ubuntu 20.04 Focal Fossa, Windows 10, or most any Linux distribution Requirements, Conventions or Software Version Used Downgrading to WSL 1 does not really work for me either, due to various compatibility and performance issues.Ubuntu 20.04 Focal Fossa running on a virtual machine in VirtualBox Software Requirements and Linux Command Line Conventions Category So unfortunately, despite all the great advantages of WSL 2, it is not to a viable solution, because I often need to run VirtualBoxes and every time deinstalling the "Virtual Machine Platform" and rebooting the computer before I can do this is just too cumbersome. What I find particularly problematic is that there is no official statement of Microsoft or Oracle that they recognize the issue and are working on it, I cannot find any dedicated tickets for this on either side. Other people are reporting similar problems with WSL 2 and VirtualBox, e.g. So it looks like that WSL 2 currently cannot coexist with VirtualBox, at least not with the current version 6.1.12 which I am using. The problem manifests itself in very slow performance, core dumps and screen staying black after booting e.g. Installing "Windows Hypervisor Platform" as mentioned by did not change anything for me. If you want to use WSL 2, you need to install the "Virtual Machine Platform" feature - but as soon as you do that, VirtualBox does not work properly any more. This is a duplicate of #536, but that issue is closed and I see no way to reopen it. Worse yet, the only way I could manage to get VB working again was to restore to before installation of WSL2 and reinstall ("Repair") VirtualBox. This happens despite the VM being configured to use HyperV and with HyperV enabled in Windows Features. Running Windows 10 version 2004 and VirtualBox 6.1, enabling WSL2 causes Ubuntu/VB to boot to a blank rectangular screen with rapidly blinking cursor.
This lets applications use the Hyper-V architecture for their emulation such as the Google Android Emulator, and VirtualBox 6 and above which are both now compatible with Hyper-V.
0 kommentar(er)
