Tried to make Win11 VM

This is for discussing general topics about how to use VirtualBox.
Post Reply
ONEEYEMAN
Posts: 23
Joined: 21. Sep 2011, 23:30
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: Ubuntu

Tried to make Win11 VM

Post by ONEEYEMAN »

Hi,
I downloaded an ISO image from MS site and tried to make a VM.

Unfortunately I was unsuccessful and was presented with the message:

"Please contact support or authorized provider and present the VBox.log file".

The file(s) are attached. The archive extension is .tar.xz. Had to rename it to .tar to submit.

Could someone please explain what I'm missing?

Thank you.
Attachments
VBox.tar
(50.77 KiB) Downloaded 102 times
multiOS
Volunteer
Posts: 1754
Joined: 14. Sep 2019, 16:51
Primary OS: Mac OS X other
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Windows, Linux, BSD
Location: United Kingdom

Re: Tried to make Win11 VM

Post by multiOS »

I've, just checked the log file and, unfortunately, I don't think I can provide any positive news, as it seems (to me) that all indications are that your Host laptop lacks the necessary resources to successfuly install/run a Windows 11 virtual machine.

The VBox.log provided shows that the VirtualBox vesrion installed is 6,1.32, which is no longer supported, i.e. the last maintenance release for the 6.1 series was 6.1.50 in January 2024, long before the releaae of Windows 11 25H2, which has it's own enhanced 'hardware' installation requirements. Windows 11 was never fully supported by VirtualBox 6.1.x although installation of earlier Windows 11 versions was possible, but only by using the same work-arounds needed to install on hardware which didn't meet the minimum requirements to bypass the validation checks performed by the Windows 11 installers.

Resource allocation issues: The log also identifies the Host system as an (Acer) Aspire 5253 with a dual-core AMD CPU
00:00:05.303467 DMI Product Name: Aspire 5253

00:00:05.303621 Host RAM: 7688MB (7.5GB) total, 3483MB (3.4GB) available

00:00:06.256735 CPUM: Logical host processors: 2 present, 2 max[, 2 online, online mask: 0000000000000003


However, the resouces allocated for the Windows 11 VM are:
00:00:05.725255 NumCPUs <integer> = 0x0000000000000002 (2)
00:00:05.725269 RamSize <integer> = 0x0000000100000000 (4 294 967 296, 4 096 MB, 4.0 GB)
00:00:39.167736 VRamSize <integer> = 0x0000000008000000 (134 217 728, 128 MB)
which clearly exceeds the 'spare capacty' available for VM and other software use; and so identifies the potential for resource conflict issues (Allocating the required 2 CPU's for the Windows VM leaves '0' for Host use; and the RAM+VRAM allocation should not exceed what's available after the Host's needs are met).

Finally, failure comes with:
00:00:39.110207 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:00:39.110215 !!
00:00:39.110216 !! VCPU0: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)
00:00:39.110436 !!
00:00:39.113225 !! Skipping ring-0 registers and stack, rcErr=VINF_EM_TRIPLE_FAULT
00:00:39.113303 !!
00:00:39.113305 !! {mappings, <NULL>}
00:00:39.113309 !!
00:00:39.113336 !!
00:00:39.113337 !! {hma, <NULL>}
00:00:39.113339 !!
A Guru Meditation error in VirtualBox typically occurs due to a critical failure in the virtual machine's execution, often related to either hardware or configuration issues. This error suggests that the virtual machine encountered a serious problem that prevented it from running, probably, based on the VBox.log output surrounding the above message, related to memory management.
ONEEYEMAN
Posts: 23
Joined: 21. Sep 2011, 23:30
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: Ubuntu

Re: Tried to make Win11 VM

Post by ONEEYEMAN »

Hi,
multiOS wrote: 16. Aug 2026, 22:24 I've, just checked the log file and, unfortunately, I don't think I can provide any positive news, as it seems (to me) that all indications are that your Host laptop lacks the necessary resources to successfuly install/run a Windows 11 virtual machine.

The VBox.log provided shows that the VirtualBox vesrion installed is 6,1.32, which is no longer supported, i.e. the last maintenance release for the 6.1 series was 6.1.50 in January 2024, long before the releaae of Windows 11 25H2, which has it's own enhanced 'hardware' installation requirements. Windows 11 was never fully supported by VirtualBox 6.1.x although installation of earlier Windows 11 versions was possible, but only by using the same work-arounds needed to install on hardware which didn't meet the minimum requirements to bypass the validation checks performed by the Windows 11 installers.

Resource allocation issues: The log also identifies the Host system as an (Acer) Aspire 5253 with a dual-core AMD CPU
00:00:05.303467 DMI Product Name: Aspire 5253

00:00:05.303621 Host RAM: 7688MB (7.5GB) total, 3483MB (3.4GB) available

00:00:06.256735 CPUM: Logical host processors: 2 present, 2 max[, 2 online, online mask: 0000000000000003


However, the resouces allocated for the Windows 11 VM are:
00:00:05.725255 NumCPUs <integer> = 0x0000000000000002 (2)
00:00:05.725269 RamSize <integer> = 0x0000000100000000 (4 294 967 296, 4 096 MB, 4.0 GB)
00:00:39.167736 VRamSize <integer> = 0x0000000008000000 (134 217 728, 128 MB)
which clearly exceeds the 'spare capacty' available for VM and other software use; and so identifies the potential for resource conflict issues (Allocating the required 2 CPU's for the Windows VM leaves '0' for Host use; and the RAM+VRAM allocation should not exceed what's available after the Host's needs are met).

Finally, failure comes with:
00:00:39.110207 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:00:39.110215 !!
00:00:39.110216 !! VCPU0: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)
00:00:39.110436 !!
00:00:39.113225 !! Skipping ring-0 registers and stack, rcErr=VINF_EM_TRIPLE_FAULT
00:00:39.113303 !!
00:00:39.113305 !! {mappings, <NULL>}
00:00:39.113309 !!
00:00:39.113336 !!
00:00:39.113337 !! {hma, <NULL>}
00:00:39.113339 !!
A Guru Meditation error in VirtualBox typically occurs due to a critical failure in the virtual machine's execution, often related to either hardware or configuration issues. This error suggests that the virtual machine encountered a serious problem that prevented it from running, probably, based on the VBox.log output surrounding the above message, related to memory management.
Thank you for the explanation.

I'll try to upgrade the VB and see if it can be installed.
Post Reply