Ubuntu 17.10.1 running slowly

[jordanbaron]

I have installed Ubuntu 17.10.1 but the UI is very slow. I have installed guest additions, turned up the VRAM, turned up the RAM to 4GB, and turned on 3D acceleration. I also have hardware virtualization on. I don't know what to do next.

[socratis]

I don't know what to do next.

Start by posting a VM log from a complete VM run:

• Start the VM from cold-boot (not from a paused or saved state) / Observe error / Shutdown the VM (force close it if you have to).
• With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
• Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.

[jordanbaron]

Here you go my good man! (or woman)

[socratis]

VirtualBox VM 5.2.4 r119785 win.amd64 (Dec 18 2017 15:47:18) release log

Please update to the latest. Ubuntu 17.10 is relatively new and fixes are still coming in. The newer VirtualBox, the better. We're at 5.2.8 now. Eject the GAs CD, shutdown the VM and upgrade VirtualBox. Then re-install the GAs.

00:00:02.895625 Host RAM: 8139MB (7.9GB) total, 1697MB available
00:00:04.138030 RamSize <integer> = 0x00000000ff600000 (4 284 481 536, 4 086 MB, 3.9 GB)

You are assigning memory to your guest, that you do not have available. Either close some applications on the host, buy more RAM for the host, or reduce the amount of RAM assigned to the guest.

00:00:04.793257 CPUM: Physical host cores: 2
00:00:04.138027 NumCPUs <integer> = 0x0000000000000002 (2)

You have assigned all your CPUs to the VM. The host is going to run low on resources, since VirtualBox cares about physical processors (cores), not logical ones (threads). See "CPU Cores versus threads" and "Why is it a bad idea to allocate as many VCPUs as there are physical CPUs?". And yes, your i3-6100 has 2 cores.

00:00:04.057607 supR3HardenedErrorV: supR3HardenedScreenImage/NtCreateSection: cached rc=VERR_BAD_EXE_FORMAT
    fImage=1 fProtect=0x2 fAccess=0x5 cHits=1 \Device\HarddiskVolume1\Windows\System32\DriverStore\FileRepository\
    c0318486.inf_amd64_11ba0b4b7cc81d52\atikmdag.sys

I don't particularly like that part. Read ''__really carefully__'' the following FAQ: [viewtopic.php?f=25&t=82106 Diagnosing VirtualBox Hardening Issues] for some guidelines/ideas. This might be throwing away your 3D support.

00:00:04.138138 ICH9 <integer> = 0x0000000000000001 (1)

Any particular reason that you chose to modify the defaults and choose something that you're not suppose to chose unless you're using an OSX guest, only? Something that is labelled clearly as experimental, not recommended?