virtualbox.org

First post. I've read the forum posting guide but I'm sure there are unwritten rules. I'll try my best.

Sorry to hop in here without a whole lot of log files and the saga. I'm not going to be shy. I don't know what I'm doing. Each supporting piece of software related to virtualization and software development is an entire area of specialization that could each be a career. I'm trying to do my due diligence.

I have WSL running on windows 10 without issue but it doesn't have USB support so it's worthless to me.
I was running a 64but ubuntu VM on 6.1 + Extension pack without issues in order to create FPGA binaries using Xilinx ISE. Getting that to work on ubuntu in 64bit vm was itself an effort that took me a month.
Then wanted to check out Docker so I installed Docker Desktop and when I installed the Docker plugin in VSCode it promted me to install a WSL Kernel Module.

I think it's worth noting that this is the exact time that I got this same error discussed here... Immediately after I installed docker and the WSL Kernel update.

I don't know where to to look or who to ask about compatibility issues, coincidence may not be causation but then it might be why mine broke. Searching for solutions on this kind of stuff is a slippery slope sometimes, especially when OS's and features of vbox change. I don't want to assume a whole lot and start following instructions that aren't relevant.

In any case it seems like I'm circling down a recursive rabbithole of workarounds and alternate virtualization methods and I'm starting to get a little unhinged.

It seems that the community takes their experience for granted. I'd like to leverage that without just being a nag and making it someone elses problem.

Having said all this do any of you know if WSL/Docker/Virtualbox on 64bit windows with 64bit causes this?

Greetings, Kritischer! Welcome to the forum, we'll be happy to help.

I moved your post into its own topic, so we can help without confusing the original topic.

There's one word in your post that fairly certainly indicates what the problem is ( ):

Kritischer wrote:Docker

Docker on Windows enables Hyper-V, Hyper-V up-ends Virtualbox. The first version of WSL did not use Hyper-V and so ran alongside Virtualbox just fine. WSL2 also enables Hyper-V.

Hyper-V is a type-1 hypervisor, which runs on the bare metal under the host PC's Windows 10 operating system, making the computer's Windows 10 run as a VM already. Hyper-V uses the "Virtualization Technology" (VT-x/AMD-V) before Virtualbox can get to it, and causes errors. The Virtualbox developers are trying to get Virtualbox to run correctly when Hyper-V is enabled, but it's not all there yet, partly because Microsoft keeps moving the target.

Please right-click the VM in the main Virtualbox window's VM list, choose Show Log.

Search the far left tab's log for this text:

Attempting fall back to NEM

If you find it, Hyper-V is enabled and needs to be disabled. See HMR3Init: Attempting fall back to NEM (Hyper-V is active).

If you don't find that text, save the far left tab's log, zip the log file, and post the zip file, using the forum's Upload Attachment tab.