Very slow guest VMs in 64-bit Windows (10 & 11) hosts after upgrading VirtualBox v6.1.30 to v6.1.32.

[Ant]

​https://forums.virtualbox.org/viewtopic.php?f=6&t=104993&p=512044 for my forum thread with our details, logs, etc. Basically, our guest VMs are unusable due to being very slow. We had to downgrade back to v6.1.30 to reuse them. :(

[dannoparker]

I'm having this issue as well. The Windows Server 2016 VM will not boot. CPU spikes to max the RAM usages showed 0 total when I have 8GB provisioned to it. My host is on Windows 11

[riramar]

Same problems here. After upgrading from v6.1.30 to v6.1.32 running under Win10 all my Linux VMs are very slow during the boot.

[Sadeq Aramideh]

Hi,

Same issue here, in the change log for v 6.1.32 at https://www.virtualbox.org/wiki/Changelog-6.1 they stated that "VMM: Changed the guest RAM management when using Hyper-V to be more compatible with HVCI (bug #20627 and #20694) " which I believe is causing this issue and the fix is also buggy.

had to convert my image to use it with Microsoft vmware. Hope they fix this issue soon.

[ci-zephyurus]

I think I am having the same issue. Host Windows 10 Pro

Guest Debian GNU/Linux 11

VBox: 6.1.32 r149290 (Qt5.6.2)

In my case, the guest linux reported very high IOWAIT when I　check it with iostat command. The IOWAIT is so long and actually during booting, one of the virtual drive response was so delayed that the guest linux driver reported disk error (timeout) and refused to recognize the virtual disk drive and thus the mount failed (!).

Eventually, I had to disable hypervisorlaunchtype as mentioned in MS document. (I think I accidentally or intentionally enabled this but did not realize it. I wanted to test WINDOWS SANDBOX.

The following command would print out something like the following.

bcdedit /enum | find "hypervisorlaunchtype"

If this says

hypervisorlaunchtype Auto

Then we have to turn it off.

If it is off to start with. Fine.

hypervisorlaunchtype Off

How to turn it off. Do the following as superuser.

bcdedit /set hypervisorlaunchtype off

And reboot the host.

For now, this solved the slow I/O issue in guest system.

HOWEVER, this obviously disables the host window10 (and presumably 11 as well) features that require hypervisor function such as Device Guard and Credential Guard AND WINDOWS　SANDBOX.

I had enabled WINDOWS SANDBOX feature not knowing this would start windows hypervisor function at startup automagically. This resulted in my slow disk IO problem inside VBox guest.

Since Windows SANDBOX feature seems so nice, it would be great if 6.1.36 can be fixed to work with these functionalities of Windows nicely IF my reading of other people's comment that 6.1.32 seemed to work with such features (?).

Just a data point.

Also, it would be nice to warn at the startup time that "hypervisor function is enabled on host and it may interfere with VBox". That would have saved me a lot of google search and experiment to figure out the cause of the virtual disk drive problem. I believe such a warning at startup time of VBox will also give many users a clue when performance is bad.

TIA