virtualbox.org

I've been using VB for quite a while with no problems. Yesterday I decided to install WSL to experiment with some Docker images. I had a problem installing WSL, and after some hunting I found a solution: https://github.com/microsoft/WSL/issues ... -729914763

I did as it directed, and that solved the problem. I installed WSL and played with Docker for a while.

Today I tried to use VirtualBox, and NONE of my VMs will run. They all abort with the error "Failed to open a session for the virtual machine XXX." Even a brand-new empty VM fails; I created a new VM, ran it, it prompted for a start-up disk, and as soon as I provided the disk, the VM died.

Any suggestions?
Running VirtualBox 6.0.18 r136238 (Qt5.6.2) on Windows 10 Pro 20H2, build 19042.928.

WSL2 enables the Windows hypervisor which will interfere with the operation of VirtualBox. See this post.

viewtopic.php?f=25&t=99390

Ugh. So I can run WSL and Docker, OR I can run VirtualBox? Groan.

Guess I'll have to run Docker in a Linux VM.

Thanks for the pointer.

Ugh again. I followed those instructions. I also uninstalled WSL and updated to VB 6.1.20. Then I shut Windows down, started up again, and my VMs still didn't work.

For the benefit of anyone else who has the same problem and finds this:

Just as I was testing the VMs, WSL started up.

I looked in Windows Features and sure enough, there was a WSL feature enabled. Disabled that, rebooted. VirtualBox still didn't work. I got a message that Docker couldn't start up because WSL wasn't running. OK fine, go uninstall Docker. Reboot.

VirtualBox VMs STILL will not run.

No wait! Previously-existing VMs will not run. If I create a brand new VM, it WILL run.

So I'm making progress. But I have many stored VMs with many many hours of work in them, and I'd like to be able to use them again. So I dug through the log files -- see below. Looks like a problem with USB. Sure enough, if I disable USB2.0 in the VM, it works.

But... it also mentions a possible incompatible version of the Extension Pack. I haven't updated VBox in 2 years so I had completely forgotten about that. I updated to the current Ext Pack and shazam! All is working.
Gary

Code: Select all

00:00:03.576616 Guest OS type: 'RedHat_64'
00:00:03.577487 fHMForced=true - No raw-mode support in this build!
00:00:03.579479 VMSetError: F:\tinderbox\win-6.1\src\VBox\Main\src-client\ConsoleImpl2.cpp(1969) int __cdecl Console::i_configConstructorInner(struct UVM *,struct VM *,class util::AutoWriteLock *); rc=VERR_NOT_FOUND
00:00:03.579482 VMSetError: Implementation of the USB 2.0 controller not found!
00:00:03.579483 Because the USB 2.0 controller state is part of the saved VM state, the VM cannot be started. To fix this problem, either install the 'Oracle VM VirtualBox Extension Pack' or disable USB 2.0 support in the VM settings.
00:00:03.579483 Note! This error could also mean that an incompatible version of the 'Oracle VM VirtualBox Extension Pack' is installed
00:00:03.580014 Constructor failed with rc=VERR_NOT_FOUND pfnCFGMConstructor=00007ffcad8b1c20
00:00:03.580554 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Implementation of the USB 2.0 controller not found!
00:00:03.580591 Because the USB 2.0 controller state is part of the saved VM state, the VM cannot be started. To fix this problem, either install the 'Oracle VM VirtualBox Extension Pack' or disable USB 2.0 support in the VM settings.
00:00:03.580591 Note! This error could also mean that an incompatible version of the 'Oracle VM VirtualBox Extension Pack' is installed (VERR_NOT_FOUND)}, preserve=false aResultDetail=-78
00:00:03.581113 Console: Machine state changed to 'PoweredOff'
00:00:03.595724 Power up failed (vrc=VERR_NOT_FOUND, rc=E_FAIL (0X80004005))

A full log, zipped and posted with the forum's Upload Attachment tab, is better than a log snippet.

Extension Pack version must match the Virtualbox version.

So your VMs are all working now?

The snippet included probably 2/3 of the content, and the rest didn't seem important. I believe the attached (complete) log represents the typical case.

Yes, all VMs seem OK now.

00:00:03.308204 VirtualBox VM 6.1.20 r143896 win.amd64 (Apr 20 2021 05:23:38) release log
00:00:03.425971 Oracle VM VirtualBox Extension Pack (Version: 6.0.18 r136238;

That Extension Pack was really long in the tooth!

Glad you're up and running!

virtualbox.org

Installing WSL on Windows breaks VirtualBox?

Installing WSL on Windows breaks VirtualBox?

Re: Installing WSL on Windows breaks VirtualBox?

Re: Installing WSL on Windows breaks VirtualBox?

Re: Installing WSL on Windows breaks VirtualBox?

Re: Installing WSL on Windows breaks VirtualBox?

Re: Installing WSL on Windows breaks VirtualBox?

Re: Installing WSL on Windows breaks VirtualBox?