Those 'log errors' can be ignored. They come from a small recoverable bug in the Linux driver for the VMSVGA video card for the VM. The VM OS continues to boot correctly if there are no other problems.
The screenshot shows properly-running VM 'hardware' and an OS inside the VM that is having problems and can be troubleshot using Ubuntu's normal methods and help channels.
Ubuntu is known to go blackscreen if there is not enough free disk space to start the desktop environment. This happens in real PCs too. The solution is to log on text-only and delete stuff until the desktop environment can start. Web-search how to fix this in an Ubuntu PC and apply the steps to the VM. Also see
How to Resize a DriveAlternatively, 7-zip on the Windows host can in some cases open the VM's disk file to extract documents within. Or you can attach the VM's disk to another working Ubuntu VM. Note that if you're using snapshots, you'll have to clone the final snapshot with Mpack's
CloneVDI and attach the clone to use either of these options. And if you're encrypting the VM, then your only option is to get the VM OS running.