VirtualBox suddenly runs all VM's terribly slow

[Bretonator]

I have been working with VBox on a Windows 10 host for over a year. I run linux guests on it and things usually work great. I went to school yesterday and used my laptop until the low battery warning came on. I finished at school, came home and needed to close and restart the VM since the network connection was started up on the school network, it thought I was still there and wouldn't connect to my home network. This is a usual issue when I connect on one network and then move, VMs running don't pick up on the change, even though the host OS is agile enough to just connect.

After restarting, everything runs slow. It takes forever to load just a facebook page in chromium on my Lubuntu VM, terminal keystrokes have a 2-3 second delay. It's nearly impossible to get any work done.

I tested other VMs. I have some CentOS VMs and they run badly too. Just two days ago things were fine for all VMs on VBox.
I've tried restarting everything. Windows 10 updated itself a few days ago. I made sure my power settings are on High Performance when plugged in. I've got the Lubuntu VM (which is my primary development VM) set to 128 MB video memory, 3D acceleration enabled, 4 processors enabled, 8192 Mb RAM allocated. This thing should be running great.

I'm attempting uninstalling VBox and then Re-Installing fresh. I need to get this solved because finals are here and I can't get my React work done very well on the Windows Host.
Any help or suggestions are appreciated and I'm happy to answer questions quickly.

[Bretonator]

I've re-installed VirtualBox and updated to the latest Guest Additions release (5.2.22). Nothing has improved.

[socratis]

We need to see a complete VBox.log, from a complete VM run:

• Start the VM from cold-boot (not from a paused or saved state) / Observe error / Shutdown the VM (force close it if you have to).
• With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
• Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.

[Bretonator]

Absolutely. Here's the log, zipped up.

[socratis]

Just as I suspected, you have a hardening problem.

00:00:09.660823 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting
	'C:\WINDOWS\System32\DriverStore\FileRepository\nvlt. inf_amd64_69e4c7878f63d898\nvinitx.dll'
	(C:\WINDOWS\System32\DriverStore\FileRepository\nvlt.
	inf_amd64_69e4c7878f63d898\nvinitx.dll): rcNt=0xc0000190

Please read really carefully the following FAQ: Diagnosing VirtualBox Hardening Issues. In your case your Nvidia drivers are being rejected. You need to upgrade (or downgrade) them until you are not getting rejections.

In the place where you found the VBox.log, there's another one VBoxHardening.log. Read the above link, you'll know what to do. If not, we're here...

[Bretonator]

Getting right on it. Thanks for pointing in the right direction. I have no idea what a 'hardening' issue is.

[socratis]

I gave you a link to read
BTW, this does not belong in the "Linux Hosts" but in the "Windows Hosts" section, moving it.

[Bretonator]

Wait a minute. The guide says if I have an exit code of 0, I don't have a hardening problem. That's what it appears to be. It's 0x0 in hex, but I think that's still zero.
So does this mean I have a hardening issue?

[socratis]

So does this mean I have a hardening issue?

Yes, because you have to look in two places, both the VBoxHardening.log and the VBox.log.

• For the VBox.log, you need to search for the string "supR3HardenedError". If you do find it, see what's rejected, like above. Usually the video drivers.
• For the VBoxHardening.log, you need to 1) look for the "ExitCode", 2) search for the string "adversaries" and "rejecting". If you do find it, usually the system driver responsible is close by. Usually the antivirus.

The VBox.log is for runtime rejections, the VBoxHardening.log is for startup rejections, when VirtualBox won't even launch a VM.

For example, your VBoxHardening.log contains the word "adversaries" right next to CylancePROTECT, a known "troublemaker". But, since you can launch your VM, that means that the version you have is indeed correctly signed, so no problem. You have other DLLs being rejected, like the OneDrive one, but they're not fatal.

[socratis]

A couple more tips...

00:00:10.918718 NumCPUs <integer> = 0x0000000000000004 (4)
00:00:13.741206 CPUM: Physical host cores: 4

You have assigned all your CPUs to the VM. The host is going to run low on resources, since VirtualBox cares about physical processors (cores), not logical ones (threads). Maximum for the guest should be no more than 3.

00:01:03.952547 VMMDev: Guest Additions information report: Version 5.2.8 r121009 '5.2.8'

You need to update the Guest Additions to the current ones.

[Bretonator]

I have updated the guest additions. The latest I have installed is 5.2.22. This hasn't seemed to help.
I've found a whole lot of 'adversary' and 'rejectings' in the logs.

Code: Select all

Line 2540: 1994.25f4: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\WINDOWS\System32\DriverStore\FileRepository\nvlt.inf_amd64_69e4c7878f63d898\nvinitx.dll' (C:\WINDOWS\System32\DriverStore\FileRepository\nvlt.inf_amd64_69e4c7878f63d898\nvinitx.dll): rcNt=0xc0000190
	Line 4179: 1994.3868: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Users\linne\AppData\Local\Microsoft\OneDrive\18.192.0920.0015\amd64\FileSyncShell64.dll' (C:\Users\linne\AppData\Local\Microsoft\OneDrive\18.192.0920.0015\amd64\FileSyncShell64.dll): rcNt=0xc0000190
	Line 4185: 1994.3868: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Users\linne\AppData\Local\Microsoft\OneDrive\18.192.0920.0015\amd64\FileSyncShell64.dll' (C:\Users\linne\AppData\Local\Microsoft\OneDrive\18.192.0920.0015\amd64\FileSyncShell64.dll): rcNt=0xc0000190
	Line 4191: 1994.3868: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Users\linne\AppData\Local\Microsoft\OneDrive\18.192.0920.0015\amd64\FileSyncShell64.dll' (C:\Users\linne\AppData\Local\Microsoft\OneDrive\18.192.0920.0015\amd64\FileSyncShell64.dll): rcNt=0xc0000190
	Line 4197: 1994.3868: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Users\linne\AppData\Local\Microsoft\OneDrive\18.192.0920.0015\amd64\FileSyncShell64.dll' (C:\Users\linne\AppData\Local\Microsoft\OneDrive\18.192.0920.0015\amd64\FileSyncShell64.dll): rcNt=0xc0000190
	Line 4203: 1994.3868: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Users\linne\AppData\Local\Microsoft\OneDrive\18.192.0920.0015\amd64\FileSyncShell64.dll' (C:\Users\linne\AppData\Local\Microsoft\OneDrive\18.192.0920.0015\amd64\FileSyncShell64.dll): rcNt=0xc0000190
	Line 4209: 1994.3868: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Users\linne\AppData\Local\Microsoft\OneDrive\18.192.0920.0015\amd64\FileSyncShell64.dll' (C:\Users\linne\AppData\Local\Microsoft\OneDrive\18.192.0920.0015\amd64\FileSyncShell64.dll): rcNt=0xc0000190
	Line 4402: 1994.1208: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Users\linne\AppData\Local\Microsoft\OneDrive\18.192.0920.0015\amd64\FileSyncShell64.dll' (C:\Users\linne\AppData\Local\Microsoft\OneDrive\18.192.0920.0015\amd64\FileSyncShell64.dll): rcNt=0xc0000190
	Line 4408: 1994.1208: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Users\linne\AppData\Local\Microsoft\OneDrive\18.192.0920.0015\amd64\FileSyncShell64.dll' (C:\Users\linne\AppData\Local\Microsoft\OneDrive\18.192.0920.0015\amd64\FileSyncShell64.dll): rcNt=0xc0000190
	Line 4414: 1994.1208: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Users\linne\AppData\Local\Microsoft\OneDrive\18.192.0920.0015\amd64\FileSyncShell64.dll' (C:\Users\linne\AppData\Local\Microsoft\OneDrive\18.192.0920.0015\amd64\FileSyncShell64.dll): rcNt=0xc0000190
	Line 4427: 1994.30b0: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Users\linne\AppData\Local\Microsoft\OneDrive\18.192.0920.0015\amd64\FileSyncShell64.dll' (C:\Users\linne\AppData\Local\Microsoft\OneDrive\18.192.0920.0015\amd64\FileSyncShell64.dll): rcNt=0xc0000190

It seems that the big problem is this FileSyncShell64.dll. At least if I'm understanding this right. I have virtually no experience dealing with this sort of issue. This looks like the most complicated problem I've ever had to try to fix on a computer. If it is FileSyncShell64.dll, then what do I do?

[socratis]

Did you fix the Nvidia drivers issue in your host? That's the most important ones.
I told you, if you're getting an ExitCode=0, then don't worry particularly about the VBoxHardening.log.

[Bretonator]

I'm working on upgrading the NVidia Driver first. I'll see if that does anything. If not I may have to find an older one and try it.
I was also thinking that doing a system restore to an earlier date, from a couple weeks ago might do what I need it to do. What do you think of that?

[socratis]

I'm working on upgrading the NVidia Driver first

Great. And remember to keep searching the VBox.log after each attempt for the string "supR3HardenedError", until you don't have it anymore.

As for the restore, sure, it has helped people in the past. But eventually the system will update itself again.

[Bretonator]

I've updated the driver. The "supR3HardenedErrorV" is still occurring but it is different.
Before update:

Code: Select all

00:00:09.659961 
: supR3HardenedScreenImage/LdrLoadDll: rc=VERR_CR_PKCS7_KEY_USAGE_MISMATCH fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume2\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_69e4c7878f63d898\nvinitx.dll: fKeyUsage=0x0, missing 0x1: \Device\HarddiskVolume2\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_69e4c7878f63d898\nvinitx.dll
00:00:09.660823 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\WINDOWS\System32\DriverStore\FileRepository\nvlt.inf_amd64_69e4c7878f63d898\nvinitx.dll' (C:\WINDOWS\System32\DriverStore\FileRepository\nvlt.inf_amd64_69e4c7878f63d898\nvinitx.dll): rcNt=0xc0000190

after update:

Code: Select all

00:00:02.439156 
supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: rc=VERR_CR_PKCS7_KEY_USAGE_MISMATCH fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume2\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_d613f213e41de006\nvdlistx.dll: fKeyUsage=0x0, missing 0x1: \Device\HarddiskVolume2\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_d613f213e41de006\nvdlistx.dll
00:00:02.439370 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\WINDOWS\System32\DriverStore\FileRepository\nvlt.inf_amd64_d613f213e41de006\nvdlistx.dll' (C:\WINDOWS\System32\DriverStore\FileRepository\nvlt.inf_amd64_d613f213e41de006\nvdlistx.dll): rcNt=0xc0000190

VBox IS also running things better. I'm not sure if it will stay that way though. I also shut down the computer hard. Before I'd only done re-starts. I just held the power button and killed it cold, waited 10 seconds and restarted. VirtualBox was behaving better afterward, but the logs are still as you see. I'm not sure what to make of it. I'm not complaining, and I'll take it for now so I can get my finals done. I want to figure out what's still causing the supR3HardenedErrorV. Here's uploads of the logs after the update.