virtualbox.org

I'm running Windows 10 enterprise host (core i7-9700K, 32 GB RAM), and I have been running a WIndows 10 guest in the past.
I have also pretty frequently updated Virtualbox as well, now the latest 6.1.32.
Now a Windows 10 guest vm I've used in the past has become unusable... it starts to load, but hours later it's still loading.
Host CPU utilization hovers around 70% (the guest is given 4 CPUs / 8 GB RAM).

I installed a new Win 10 guest, with 1 CPU and 8 GB RAM, installed fine. I let the guest install all Win 10 updates as well.
Shut down guest, change the VM to use 4 CPUs, and the VM became extremely slow again.... hours later still not up,
and host CPU utilization is ~70% again.

I also tried installing another WIndows 10 guest, with 4 CPUs to start with, and in this case the installation process becomes slow,
two hours later the installer is still unpacking files.

Any hints appreciated... any older version of Virtulabox I should revert to?

VirtualBox VMs slowed to a crawl on a Win10/Win11 host nearly always means that you have Hyper-v enabled.

HMR3Init: Attempting fall back to NEM (Hyper-V is active).

Indeed it was enabled... totally forgot that I recently installed WSL2 which turned hyperv on .. thx for the tip

Since I also need WSL2, I ended up converting the win10 image in question to vhd (user vboxmanage), and imported that with hyperv manager... works now

VB 6.1.30 and HyperV work together on W10 along with WSL2. In have this setup working with the GWSL X server.

AndyCot wrote:VB 6.1.30 and HyperV work together on W10 along with WSL2

For some people, perhaps.

Please post link for contrary.

See Discuss the 6.1.30 release.

Every release version X gets people who swear that X-1 or X-2 was better. For them that may be true. I have helped people with many Hyper-v conflicts and performance hits in every release.

Now, if you don't mind, you should open your own topic if you want to have a peripheral discussion.