VirtualBox 6.1.32 shuts down critical error. [SOLVED]

[amdvbox]

Hello,

until a few days ago, my VM worked perfectly fine (and has been for weeks).
However, today when I started the VM, it worked at first. For about 5 to 10 Minutes.
Then it shut down with some kind of critical error message.
I tried it again, two or three times. Each time, the error message appeared right during booting.
I went to my BIOS checking whether AMD-V is activated. Then after reboot I tried it again.
Exact same thing happened as before. First start, it worked for 5-10 Min, then failed, afterwards failed during booting.

I have no other VMs installed.
The only programs I installed / updated in the meantime were related to crypto-mining, but also not running on a VM.

I attached the Logfile, omitting about the upper half because there were UserNames in it. I hope, information is still sufficient.

Thanks in advance.

Edit: Forgot to mention, I'm running a Windows 7 OS.

[mpack]

I attached the Logfile, omitting about the upper half because there were UserNames in it. I hope, information is still sufficient.

It is not sufficient. Please provide the complete unedited log, zipped so that it will be below the size limit.

Knowing your user name on your PC does not help anyone hack it.

[amdvbox]

Okay, here is the complete log file.

[mpack]

00:00:02.732091 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:00:02.732091 !!
00:00:02.732091 !! VCPU0: Guru Meditation -4054 (VERR_SVM_IN_USE)
00:00:02.732132 !!

A nice clear error message. SVM is the AMD name for their hardware virtualization feature, and since this resource is not managed by the OS it can only be used by one app at a time. So VirtualBox can't run when another app is using it.

"SVM in use" could mean that you have another VM platform running, or (more likely given a recent spate of this affecting Win7 hosts) - your chosen third party antivirus has started using SVM.

[amdvbox]

Yes, the Antivirus was the most recent software updating itself.
So that's probably it.
I have contacted AVG, and will report back as soon as I have a solution.

Thanks a lot.

[amdvbox]

Turns out, there already was an option to resolve this.

- go to AVG Menu -> Settings -> General -> Troubleshooting;
- un-check "Enable hardware-assisted virtualization";
- reboot the computer;
- enjoy VM again.

[mpack]

Thanks for reporting back.