MsEdge W10 VM failing to run on Virtualbox

[Real McCoy]

Hey

"A critical error has occurred while running the virtual machine and the machine execution has been stopped"

I am currently running W10 and I am trying to run a W10 VM on VirtualBox however it keeps crashing on starting.

"
00:00:41.044417 GIM: HyperV: Resetting MMIO2 regions and MSRs
00:00:41.050843 Changing the VM state from 'DESTROYING' to 'TERMINATED'
00:00:41.076602 Console: Machine state changed to 'PoweredOff'
00:00:42.679407 GUI: Passing request to close Runtime UI from machine-logic to UI session.
".

I have the log file but it is too large to attach, can I just copy paste the text?

What info do you need to help me out?

Thanks

[mpack]

I have the log file but it is too large to attach, can I just copy paste the text?

Zip the log, then attach.

[Real McCoy]

Right... Slipped my mind. See attached

[mpack]

The idea of a VM is that the VM can use resources that the host can do without.

00:00:03.347349 Host RAM: 3981MB (3.8GB) total, 1612MB available
...
00:00:03.566175 RamSize <integer> = 0x0000000100000000 (4 294 967 296, 4 096 MB, 4.0 GB)
00:00:03.566434 VRamSize <integer> = 0x0000000000800000 (8 388 608, 8 MB)

How can you expect to give a VM 4GB RAM when that is 100% of what the host has? Making no allowance for what the host OS needs?

And no modern OS is going to run with an 8MB graphics RAM allocation either.

And I see the host CPU only has two cores, with the VM getting one.

You should cut the VM RAM to 1024MB. Increase graphics RAM to 64MB. Allocate 2 vCPUs.

But basically: you can't squeeze a 2 quarts into one pint pot. One copy of Win10-64bit is pretty much all that your PC can handle with ease.

[Real McCoy]

Great. Thanks