I have Virtual Machine Platform and Windows Hypervisor Platform installed.
If it works in a satisfactory way I may abandon VBox on Windows. I just reinstalled VirtualBox 6.1.14 as @xwh16 suggested. "Windows Hypervisor Platform" and "Virtual Machine Platform" disabled. @mrxdkox For me, 6.1.16 works quite well with Linux guests. 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. Switching to Mac now with work migrating ... VirtualBox Version 6.1.16 r140961 (Qt5.6.2) - NOT working with WSL2. 启动wsl时报错: ==参考的对象类型不支持尝试的操作==2.切换wsl版本失败: ==请启用虚拟机平台==5.效果展示6. 前提要求2.Windows 2004中的wsl2新特性3.步骤1. It's much slower than normal even with 8GB RAM, 128MB VRAM, and 4 processors allocated.
Quiet sad for WSL2 Docker Desktop, Windows never stand well with Linux.
(I left it overnight last time and nothing happened after that last message). 启动wsl时报错: ==参考的对象类型不支持尝试的操作==2. 步骤1. For pure software I would stick with Docker.
After disabling "Virtual Machine Platform" (and reboot) everything work without any problems. After that VirtualBox didn't work anymore (as expected), but I installed the "Windows Hypervisor Platform" and installed the latest version of VirtualBox (6.1.12) and now everything is working as expected. @Cito just tried disabling "Hyper-V Platform" still no success. Unfortunately, booting a Windows guest with 6.1.16 still does not work for me, no matter how I set this option. The final kernel log line is TSC doesn't count with p0 frequency and various messages RE cgroups before that, could be a red herring. VirtualBox启用hyper-v支持2. 6.1.16 seems to work with hyper-v ok on Intel, but still broken on AMD?