virtualbox.org

Hello everyone,

im using an Windows 10 64 bit host, with AMD Phenom II X6 1100T and an NVIDIA GEFORCE GTX 970, RAM 8 GB.
My guest system is Ubuntu 20.04 64bit which i got from my professor. Virtualisation in the BIOS is enabled and also changed with the "Paravirtualisation Interface" setting from Hyper-V to Minimal to Default to None
which changed nothing.

When i start the Virtual Machine, it loads pretty normal (i see the Ubuntu sign and the loading circle animation) then a black screen and the generic message " oh no something has gone wrong"
I can log out and log back in but the error persists. The log VBoxHardening is in the attachment (for this setup).

If i use a normal Ubuntu 20.04.02 it loads like in the first guest system but it stops at the black screen and at the flashing underscore. Nothing else happens after that.
I really need this for my studies and i am willing to provide additional information if necessary.

Greetings,
Xenoshell

Not sure why you'd be so fixated on the hardening log. It shows an error code of 0, i.e. you don't have a hardening problem. The messages you quote from it are normal, nothing fatal there.

And yes, changing the paravirtualization API setting only changes the "language" used to talk to a modern guest. Please put this back the way you found it: it should be set to Auto or KVM for a Linux guest. And note that this setting has absolutely nothing to do with whatever virtualization mechanisms the host PC is using.

If you provide a zipped VM log then we can probably get to the real problem.

Hey mpack,

sorry im new to this so i just didnt know what to put as title... I added the VBox log in this comment
Ok i put it now on KVM. BTW is there a reset button for settings? Would be useful for a situation like this

Greets,

Xenoshell

I don't know if this is your only problem, but allocating RAM you don't have is never a good idea.

00:00:04.163557 Host RAM: 8190MB (7.9GB) total, 4026MB (3.9GB) available
...
00:00:04.400727 RamSize <integer> = 0x0000000100000000 (4 294 967 296, 4 096 MB, 4.0 GB)
00:00:04.401123 VRamSize <integer> = 0x0000000004000000 (67 108 864, 64 MB)

I suggest that you reduce the VM RAM allocation to 2GB, you can push it to 3GB if you must. Consider getting more RAM for this host if you want to play with 64bit VMs!

IME it's weird to see a 6 core host with only 8GB of RAM (total).

A final note: I see nothing in the log to indicate a problem with the VM. If you continue to have problems with the guest OS then I'd look to fixes within the guest OS.

In fact the VM gets a long way in, e.g. the Guest Additions are loaded (albeit from 6.1.16 - best update when possible). I'm surprised it can encounter something after that that prevents the boot from completing.

Hey mpack,

thanks for your reply. I changed RAM to 2 GB, put the CPU at 3 cores, VRAM is still at 64 MB.
I also played around with the settings a bit and activated 3D Acceleration.

I didnt think that would solve the problem, but now i can log in without any crashes or error messages just fine.

Thanks for your help

Thanks for reporting back.