6.1.32 is unusable

[wbk]

6.1.32 definitely has a couple of problems, in my mind they are minor and easily avoided except for those on Win10 or Win11 hosts who insist on enabling Hyper-v.

Heh, sorry about that With WSL2, I think a lot of people find it difficult to disable hyper-v. For Windows client virtualization with GUI, VirtualBox is still much better than hyper-v so I'd like to keep using both, if possible

Anyway, I had the exact same issue (the virtual machines become completely not usable with 6.1.32 but not with 6.1.30) so here are the logs as requested.

[scottgus1]

Split from viewtopic.php?f=6&t=105310

You've got the 6.1.32 glitch:

00:00:02.385754 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
...
6.1.32 Hyper-V Glitch (remove right 9 characters, time offset in seconds, less than 1 second normal)
00:01:30.446168 /TM/VirtualSync/CurrentOffset 56004608628 ns

Our forum guru 'fth0' has done some troubleshooting and pins down these possibilities to try (HCVI = Microsoft 'Memory Integrity'):
6.1.32 without Hyper-V
6.1.30 with Hyper-V but without HVCI
6.1.26 with Hyper-V and HVCI.

[wbk]

Hello,

1. 6.1.32 w/o hyper-v, no hvci: works (logs attached)
2. 6.1.30 w/ hyper-v, no hvci: also works (logs attached)
3. 6.1.36 w/ hyper-v, hvci: I couldn't test this because Windows says VBoxDrv.sys 6.1.26.45957 is incompatible with Memory Integrity.