VBox suddenly broken for all VMs after intense use

[corapsokugu]

Hello,

I have been using VirtualBox for years without any problems. Recently, I installed many Debian, Arch and Ubuntu distros, as rapidly as 3 at the same time in that evening. I started getting errors from them and kept trying. However errors got consistent.

My old virtual machines also got effected and they were unusable. My old Ubuntu was giving a black screen very often and I couldn't even start my Windows 10 because it looked like slow motion on booting animations and eventually get stuck on my i7 7th gen and 1050 ti notebook which isn't usual.

I tried to recreate VM's, reinstall VirtualBox (deleted ".VirtualBox" folder too). I even formatted all my disks and partitions and reinstalled my physical Windows 10. Xubuntu 20.04 still gave me errors on install but I managed to install Manjaro this time. However, after I deleted the test setup and tried to install a real one with 20 GB's of space, Manjaro also started to act weird, not starting things when I click on them, slowing down, getting stuck, just hanging and eventually giving critical errors.

I have attached 3 logs onto this post. They also include another weird behaviour which is plugging some audio device back and forth. I also noticed it myself as my notification area in host was getting spammed. My VBox is doing all sorts of weird things

My VBox version is VirtualBox-6.1.6-137129-Win.

[mpack]

00:00:04.175385 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
00:00:04.231337 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...

Same old same old. You have Hyper-v enabled.

Related FAQ, especially posts #2 and beyond. FAQ: I have a 64bit host, but can't install 64bit guests.

[corapsokugu]

Oh right, I can actually install VMs. That's why I didn't really pay attention to that header. I don't even have a specific error, it was just broken. One interesting thing I saw in that topic is WSL2 enabling Hyper-V. I have been using WSL2 along with VirtualBox before and it used to work. Is it just about running them concurrently? Other than that I will try check those steps and update my post.

Thank you.

[corapsokugu]

So after several hours, everything seems to be correct and I also have investigated NUMEROUS other pages about VT-x, Hypervisor and so on. Checked BIOS and all, nothing solved the problem so far. I keep getting what you have mentioned in the logs. This is extremely cursed. I also remember using WSL2 along with VirtualBox before. I will try to format once again for now.

[Martin]

Are you sure it was WSL2? The initial version of Windows Subsystem for Linux was using different technology which seems to have worked besides VirtualBox.