Redox OS gets a Guru Meditation Error.

[Stutav]

My host OS is Windows 10, and When I run Redox OS with KVM Acceleration, VT-x, Nested Paging, 2048 MB of RAM, using an ISO, and no graphics acceleration, It gets a Guru Meditation error. With certain settings on, it has these white lines. I am unable to get the files because they are too big, however if I can put them in Pastebin I will. I've seen dadkeyb dll errors, but I see this error I cannot find anything about. Here is 3 lines that I think might help.

Code: Select all

00:00:09.967853 Changing the VM state from 'DESTROYING' to 'TERMINATED'
00:00:09.968963 Console: Machine state changed to 'PoweredOff'
00:00:10.005963 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: cached rc=VERR_LDRVI_NOT_SIGNED fImage=1 fProtect=0x0 fAccess=0x0 cHits=4 \Device\HarddiskVolume3\Program Files\Dell\QuickSet\dadkeyb.dll

and in VBoxHardening log:

Code: Select all

1884.431c: supR3HardenedScreenImage/LdrLoadDll: cached rc=Unknown Status -22900 (0xffffa68c) fImage=1 fProtect=0x0 fAccess=0x0 cHits=8 \Device\HarddiskVolume3\Program Files\Dell\QuickSet\dadkeyb.dll
1884.431c: Error (rc=0):
1884.431c: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Program Files\Dell\QuickSet\dadkeyb.dll' (C:\Program Files\Dell\QuickSet\dadkeyb.dll): rcNt=0xc0000190
1884.431c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0xc0000190 'C:\Program Files\Dell\QuickSet\dadkeyb.dll'
1884.431c: supR3HardenedDllNotificationCallback: Unload 00007ffe05950000 LB 0x00014000 C:\WINDOWS\system32\wbem\wbemsvc.dll [flags=0x0]
1884.431c: supR3HardenedDllNotificationCallback: Unload 00007ffdf5ad0000 LB 0x0003a000 C:\WINDOWS\system32\dataexchange.dll [flags=0x0]
1884.431c: supR3HardenedDllNotificationCallback: Unload 00007ffe192b0000 LB 0x0025b000 C:\WINDOWS\system32\d3d11.dll [flags=0x0]
1884.431c: supR3HardenedDllNotificationCallback: Unload 00007ffe1b110000 LB 0x000eb000 C:\WINDOWS\system32\dxgi.dll [flags=0x0]
1884.431c: supR3HardenedDllNotificationCallback: Unload 00007ffe19970000 LB 0x001db000 C:\WINDOWS\system32\dcomp.dll [flags=0x0]
1884.431c: supR3HardenedDllNotificationCallback: Unload 00007ffe1a4a0000 LB 0x0025a000 C:\WINDOWS\system32\twinapi.appcore.dll [flags=0x0]
1884.431c: supR3HardenedDllNotificationCallback: Unload 00007ffe1a910000 LB 0x00029000 C:\WINDOWS\system32\RMCLIENT.dll [flags=0x0]
1884.431c: supR3HardenedDllNotificationCallback: Unload 00007ffe064d0000 LB 0x00101000 C:\WINDOWS\system32\wbem\fastprox.dll [flags=0x0]
1884.431c: supR3HardenedDllNotificationCallback: Unload 00007ffddefa0000 LB 0x000d5000 C:\Program Files\Oracle\VirtualBox\VBoxProxyStub.dll [flags=0x0]
1884.431c: supR3HardenedDllNotificationCallback: Unload 00007ffe07300000 LB 0x00011000 C:\WINDOWS\system32\wbem\wbemprox.dll [flags=0x0]
1884.431c: supR3HardenedDllNotificationCallback: Unload 00007ffe0ab20000 LB 0x00084000 C:\WINDOWS\SYSTEM32\wbemcomn.dll [flags=0x0]
1884.431c: supR3HardenedDllNotificationCallback: Unload 00007ffdcd0c0000 LB 0x003a4000 C:\Program Files\Oracle\VirtualBox\VBoxC.dll [flags=0x0]
1884.431c: Terminating the normal way: rcExit=0
5890.5110: supR3HardNtChildWaitFor[2]: Quitting: ExitCode=0x0 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 12839 ms, the end);
4a78.3194: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x0 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 13580 ms, the end);

If any of this helps, or if you want the whole file(s) in Pastebin, then please tell me

[fth0]

Your analysis so far has been correct. The dadkeyb.dll is part of the Dell QuickSet and Dell ControlPoint System softwares, and injects itself into running processes. VirtualBox detects this behavior and will not run any VMs. You will have to either uninstall the software, or keep it from injecting itself into processes that VirtualBox checks (see VBoxHardening.log).

Regarding file uploads: Zip them first, and they will be small enough.

[Stutav]

The dadkeyb.dll is part of the Dell QuickSet and Dell ControlPoint System softwares, and injects itself into running processes.

I removed Dell Quickset, should I remove ControlPoint because VirtualBox still gives me that error. Thank you!

EDIT: I do not have ControlPoint, and it gives me the same error

[Stutav]

Oh, and here are three files:

[fth0]

I'm not sure if I can assess your log files correctly: The VBoxHardening.log file has much more content than I expected, so it maybe is from multiple runs, and the VBox.log.3 file is the oldest of the 4 log files available.

To make sure that we see only the output from the latest run: Can you please rename the VBoxHardening.log file, start your VM, let it crash, accept the Guru Meditation, and then post the new VBoxHardening.log file and the VBox.log file (zipped, of course)?

Another hint: You chose the OS type Other. While this looks like the natural choice for a non-Windows, non-Linux OS, it probably is not, because it is the lowest common denominator regarding hardware provided to the guest OS. IMHO it would be better to choose a Linux variant that has similar capabilities as Redox OS.

[Stutav]

Sorry for late response

[fth0]

In the meantime, I tried to setup a Redox OS VM myself, using VirtualBox 5.2.34 on macOS 10.13.6, using Redox in the Live-CD version as well as the hard disk version, as well as using different guest OS types. All attempts end in the same result (as yours): The crash happens in the Redox Loader - Stage Two or later. I could imagine that the Redox OS expects hardware that is not provided by VirtualBox, but that is only a guess. (The Hardening aspect is a Windows host only topic and probably not your real problem.)

Since Redox OS is not explicitly supported by VirtualBox as a guest OS, maybe you should try using QEMU as suggested in the Redox OS Book ...

[Stutav]

When I run Qemu in WSL I get an error with KVM:

Code: Select all

Could not access KVM kernel module: No such file or directory
qemu-system-x86_64: failed to initialize KVM: No such file or directory

So I guess I can see if there is another one if I cannot fix it.