Trying to install Ubunut 16.04

[akafrog18]

I just built a new system and now I'm trying to run a virtual machine on it. Specs of the machine are below. I have VB 5.2.18 installed on Ubuntu 16.04.5. When I attempt to start a new Ubuntu 16.04.5 32bit machine, it will not run. I did turn on SVM in the UEFI of the machine. That allowed me to get further but now I'm still getting an error. Any help?

Asrock B450M Pro4 bios is 1.20
AMD Ryzen 5 2600 proc
16 GB Memory
MSI Geforce GT710 video card

[socratis]

00:00:00.289389 VRamSize <integer> = 0x0000000001000000 (16 777 216, 16 MB)

Increase the VRAM for your guest to at least 64 MB, if not 128 MB.


PS. For future reference you should ZIP your logs. It helps save a (virtual) tree or two...

[akafrog18]

Thank you for the quick reply. I updated the VRAM to 128 but I'm still getting the same error about a recursive fault and reboot. Any other suggestions to get this working?

Thanks!

[socratis]

I happen to have an Ubuntu 16.04-32bit. It's actually my favorite Ubuntu, until 18.04, I'm thinking of transitioning . And I didn't see any differences.

On top of that, I downloaded the same ISO (ubuntu-16.04.5-desktop-i386.iso) as you did, created a new VM named "Luis" as you did, increased the RAM to 2048 as you did, the VRAM to 128 as you did. So, pretty much I mirrored your setup. Not a single problem booting. And our logs look identical (no kidding).

So, can you please verify that the checksum of your ISO matches what it's supposed to be? The checksums can be found here: http://releases.ubuntu.com/16.04/ where I actually downloaded the ISO from.

[akafrog18]

Socratis, I did verify the checksum of the iso and it verified OK. I did download it again and ran the verify on the new iso. It also verified OK. I swapped out the new iso and attempted to boot again with the same error. Attached is the error I see when I run the machine. I also downloaded the Ubuntu 16.04 machine from OSBoxes.org and I receive the same error.

Are you running an AMD machine as well?

Thanks!
[ModEdit; removed almost exactly similar screenshot of stuck VM]

[socratis]

A new ZIPPED VBox.log would be preferable, compared to the almost same screenshot (except the times actually).