After upgrading from 6.1.32 to 6.1.34 Guru Meditation Debian 6 guest

[davidnd]

I'm on a 64-bit amd laptop, with windows 11 pro updated today
version: 21H2
os build: 22000.652
Experience: Windows Feature Experience Pack 1000.22000.652.0
My virtual machine is a 64-bit Debian 6, everything worked correctly before updating, I tried to revert to the same previous version, it still had the installer, and the extension pack, and nothing, it still gives the same problem.
I tried to get rid of all the virtualbox files, drivers looking through forums and even windows registry keys, trying different paravirtualization interfaces, and different configurations, removing usb 2.0, audio, network and it doesn't work.

The problem doesn't happen instantly, start grub and the operating system starts to load with menssage "Loading, please wait..." and that's when Guru Meditation occurs.

The guest additions weren't up to date on the guest machine and I don't have much more information.

I have not been able to interpret the logs and traces, I do not know how to solve it. I have another computer (win11 pro x64 updated) with virtualbox 6.1.32 and it is working with the same virtual machine. The machine comes from an ova that has been delivered to me, and I have tried to import it from scratch several times and export it from my other computer giving the same problem.

I have also checked not to have the windows features that interfere with virtualbox and to have "hypervisorlaunchtype off"

I attach the logs with the configuration before updating Vbox and VboxHardening in zip

[mpack]

Hyper-v is enabled.

00:00:06.625607 HM: HMR3Init: Attempting fall back to NEM: AMD-V is not available
00:00:06.680431 NEM: info: Found optional import WinHvPlatform.dll!WHvQueryGpaRangeDirtyBitmap.
00:00:06.680494 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...

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

[davidnd]

Thank you very much, I verified that the option I needed to get it to work was to go to Windows Defender > Device Security > Kernel Isolation Details and make sure the setting in this pane is off and reboot. Thanks to your link

I had already done this, but it was not enough:
bcdedit /set hypervisorlaunchtype disabled

DISM /Online /Disable-Feature:Microsoft-Hyper-V

Thanks for the help . I guess some windows update might have interfered.

[mpack]

I had already done this, but it was not enough:
bcdedit /set hypervisorlaunchtype disabled

That should have been enough, provided it was followed by a restart from a full power down, since "bcdedit" simply sets the parameters for the next boot, it does nothing immediately.

[davidnd]

I had already done this, but it was not enough:
bcdedit /set hypervisorlaunchtype disabled

That should have been enough, provided it was followed by a restart from a full power down, since "bcdedit" simply sets the parameters for the next boot, it does nothing immediately.

I think I had already tried it, but I just tried to activate Windows Defender Isolate Core again and it asks me to reboot, I do it, everything is correct, but Guru Meditation occurs.

I have tried to execute the bcdedit line again with the function activated, I have done poweroff and waited 30 seconds, but Guru Meditation occurs. After I deactivate the function, restart, and it works correctly again.

And I have verified that in the other computer where the vm worked, it had the function deactivated, I have not configured this since it worked until it stopped working.

[fth0]

Thanks for trying again. How is Windows Fast Startup configured on your host?