Critical error

Discussions about using Windows guests in VirtualBox.
Post Reply
kharoh
Posts: 1
Joined: 4. May 2021, 18:49

Critical error

Post by kharoh »

I'm trying to install Windows 10 on a virtual machine, keeps on going to this "Guru Mode". Can someone help me please? :)
Attachments
VBox.rar
(42.95 KiB) Downloaded 5 times
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Critical error

Post by mpack »

00:00:04.341983 Host RAM: 8108MB (7.9GB) total, 2793MB (2.7GB) available
...
00:00:04.620994 RamSize <integer> = 0x000000010a200000 (4 464 836 608, 4 258 MB, 4.1 GB)
00:00:04.621219 VRamSize <integer> = 0x0000000008000000 (134 217 728, 128 MB)
You can't assign RAM you don't have. The whole idea of a VM is to use idle resources to run a second OS, not resources that a first OS is using. I would reduce the VM RAM to 2048MB, and even then I'd investigate to find out what is hogging so much host RAM. If you want to get into VMs then you should consider adding RAM, as a 16GB host would be better if Win10 era guests are your goal.
 Edit:  I see that it's also a dual core CPU, so perhaps a better option is replacing the PC. Quad core Intel processor (i7-6xxx or better) would be my goal.

And you are trying to install Windows 10? Your log says otherwise.
00:00:04.564384 Guest OS type: 'WindowsNT_64'
Windows 10 is not noughties era NT, which is the template you chose. Win10 will not run with that template.

While I'm at it, Win10 will be a horrible experience on one core.
00:00:04.620992 NumCPUs <integer> = 0x0000000000000001 (1)
...
00:00:06.219691 CPUM: Physical host cores: 2
Your host CPU only has two cores (ideally it needs 4 cores to keep two instances of Win10 happy), so there's no ideal solution here IMO. However the best solution on this hardware (again IMO) is to assign two cores to the VM and then avoid doing heavy CPU lifting in either host or guest.

Last but certainly not least, you have Hyper-v enabled on the host, which is going to cause very poor performance and crashes.
00:00:04.621372 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
00:00:04.682813 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...
Have a read of: HMR3Init: Attempting fall back to NEM (Hyper-V is active)
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Critical error

Post by mpack »

p.s. On your CPU. I was expecting it to be an ancient laptop i3 or similar (being only two cores), but it's actually a 7th gen i3 (i3-7100T). Released in 2017 and already discontinued! Very strange! I would expect CPUs to be made for around 8 years rather than 4. I can only assume that 2 core CPUs didn't sell well by 2017, so they grabbed back the fab line for something more profitable.
Post Reply