virtualbox.org

Hello,
no matter what configuration I use, everytime I set the vCPU greater than 1 the VM crashes with Guru. I already searched for Guru and VINF_EM_TRIPLE_FAULT but it seems this is not the real problem. I can't figure out what the exact problem is so can someone else have a look into the log file please?

Edit: I made some further researches: I tried with PAE/NX enabled, I tried it with PAE/NX enabled and Nested Paging disabled. While crashing I was installing Windows 10 x64 Version 2004 from an image file. It also crashes while booting or saving the state of the vm.

I uploaded another log which is more expressive because this time I removed the nvme controller.

I tried the new version 6.1.4 but guru still occurs. Again while installing windows 10 guest on windows 10 host. The VM was a new one. I changed the vCPU to 2, checked 3D Acceleration and selected ICH9 as chipset. I will attach the log files. If you need further details about my system or the vm settings, let me know.

Both hardening logs show 0x0 exit codes, so no hardening problems.

Two of the logs mention a 'Vibranium' install disc:

00:00:22.714784 File system of 'E:\Virtual Machines\images\2004\19041.84.Vibranium-X64-DE-XXL-SUPER-MULTI.ISO' (DVD) is ntfs
00:00:01.655959 File system of 'E:\Virtual Machines\images\2004\19041.84.Vibranium-X64-DE-CLIENTPRO.ISO' (DVD) is ntfs

Please repeat your test with an official 'Microsoft Media Creation Tool'-sourced ISO.

Also try with BIOS instead of EFI.

Looks like it's woking witn BIOS instead of EFI. Can you explain me what the problem is and do I have to go with BIOS from now on or is it fixable? I didn't test it with another iso file yet.

The Virtualbox manual's part on EFI: https://www.virtualbox.org/manual/ch03.html#efi may have something pertinent to why your install ISO won't boot on EFI. If you're still using the Vibranium ISO, it may not be compatible with Virtualbox's EFI. I believe that the Media Creation Tool's Windows 10 ISO does work with EFI.

I downloaded an image from official microsoft site and with efi I still get the Guru error so I guess the image is not the trigger.

If an official MS ISO fails, then that's a good indicator something else is wrong. What, though, is beyond me.

Do you need EFI or ICH9? If not, 6.1.2's defaults for Windows 10 are BIOS and PIIX3.

I am trying a W10 install with EFI and ICH9 and 2 processors now, will report back...

Alright, thanks for your investigation. I can say that all options except amount of processors and EFI can be eliminated. And I doubt the iso file is causing the error. I also tested version 6.0.6 and it worked with all isos and EFI, I didn't encouter Guru once. I will try it with another version between 6.0.6 and 6.1.4.

To answer your questions. I don't need either but the documentation encourages to use the newer ICH9 chipset because the P2X3 is for older systems + I might be wrong but with ICH9 it feels a bit faster. I doubt that the chipset is causing issues.

Edit: VirtualBox v6.0.14 is working as well with efi, 2 CPU and ICH9.

On my 6.1.2 host, a Windows 10 2-processor guest with EFI & ICH9 installs and boots fine. The ISO is MS's Enterprise Evaluation ISO:
"18362.30.190401-1528.19h1_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_en-us.iso"

I don't have any more successful ideas myself, unfortunately. A guru will have to investigate further.

Try to see if 6.0.16 will work.

Only thing I could suggest is a Bugtracker ticket with a good detailed explanation, logs for a working 6.0.14 & failing 6.1.x guests, and a link back to this thread.

ok, for now I will do more tests and post here. Thank you!

The version 6.0.18 is the latest working for me. So the problems start with version 6.1. What do you think, should I open a new ticket?

Btw...how far does the BIOS version of the host pc affect the stability of VirtualBox? I'm asking because I have a BIOS version from 2018 and I read about Virtualbox and microcodes...

Do you have any updates on this? I have exact same problem no matter I do always get "guru meditation" on multiple CPUs. I will try to downgrade to version of VBox you mentioned.
UPDATE: I can confirm that with 6.0.18 it is working. Did you already set the ticket?

Since I can't post links, Google Search for "MicrosoftDocs WSL issues 798". My reason for this same issue was WSL and VirtualBox not playing nicely.

WSL is OK. It is only WSL2 which interferes because it uses the hardware virtualization capabilities of the CPU and prevents access by VirtualBox. Hardware virtualization is required to run multiple CPUs.