VIrtualBox wrong configuration value

[umutbalkan]

Describe the bug VirtualBox throws an error about some configuration value

To Reproduce Follow the tutorial with VirtualBox 6.1.30

Expected behavior A working VM.

Environment WIN10 both. latest

Additional context

Failed to open a session for the virtual machine shitebox1.

Failed to open system BIOS file 'C:\VBoxLdr\data\pcbios386.bin' (VERR_PATH_NOT_FOUND).

Result Code:	E_FAIL (0x80004005)
Component:	ConsoleWrap
Interface:	IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

[hfiref0x]

This project is not maintained since 08.2020. Last VBox version it was checked against was 6.1.2.

[umutbalkan]

Issue persist on VBox 6.1.2 even though I re-iterated all the steps 4 times. I cant even get to boot

[hfiref0x]

Do you have this file on disk C:\VBoxLdr\data\pcbios386.bin?

[umutbalkan]

I do, but the most recent trial with VBox 6.1.6, output changed to:

Failed to open a session for the virtual machine shitebox.

VMMR0_DO_NEM_INIT_VM failed: VERR_NEM_MISSING_KERNEL_API_2 (VERR_NEM_MISSING_KERNEL_API_2).

AMD-V is not available (VERR_SVM_NO_SVM).

Result Code:	E_FAIL (0x80004005)
Component:	ConsoleWrap
Interface:	IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

I also happen to fail at loader.exe

[>] Entering MapTsugumi
[>] Entering ProviderCreate
[>] Entering StartVulnerableDriver
[!] OpenService failed (Error 1060)
[<] Leaving StartVulnerableDriver
[<] Leaving ProviderCreate
[!] ProviderCreate failed, abort
LDR: Cannot inject monitor code
[<] Leaving VBoxLdrMain

Do I have to change some settings at BIOS? What can I do about loader.exe not working? Thanks

[hfiref0x]

[!] OpenService failed (Error 1060)

It seems that you have "Nal" driver (Intel driver that is used by this loader to load own driver) loaded, but it doesn't have corresponding service control manager entry in registry. You can try reboot machine and start loader again. If problem persist look if you have any Intel "iqvm64" (name may vary) driver loaded.

As of VERR_NEM_MISSING_KERNEL_API_2 it is something I didn't encountered before. Do you have AMD CPU? They have this ticket https://www.virtualbox.org/ticket/19779 and https://forums.virtualbox.org/viewtopic.php?f=6&t=96555 so this could be a bug that Oracle fixed in more recent VBox 6.1.x versions.