How to fix UEFI boot with startup.nsh and Antergos Linux in Virtualbox

If you’re installing Antergos in UEFI mode in Virtualbox, things won’t go so smoothly because you’ll need to setup the EFI boot. You’ll get a message like this:

EFI boot

After that it’ll go into the UEFI Interactive Shell. There, you’ll have to edit the startup.nsh script to add the efi file.

Type FS0: and press enter to open the filesystem
Type edit startup.nsh and press enter to open the editor
Type \EFI\antergos_grub\grubx64.efi and press CTRL + Q to quit, but it asks you to save the file. Do that and press enter again and CTRL + Q again to exit for real.
Type reset and press enter to restart the virtual machine and it should boot your Antergos Linux OS properly.

Virtualbox dynamically allocated vs fixed size VDI drive performance benchmark

Is there really a difference in speed?

I’ve been working more and more with Virtualbox these days. One of the dilemmas you get in the beginning is whether to create a fixed size or dynamically allocated virtual drive for the storage. The first one wastes quite a lot of space on the hardware if the space is not actually in use in the virtual machine, but while it’s supposed to be a tad faster. With the second one, the size of the drive is only as much as that is actually in use in the virtual machine. The maximum size can be anything that fits on your hardware (maybe even bigger, I haven’t tested that). So take for example these two virtual drives:

50 GB fixed size => takes up 50 GBs of space on your actual drive
50 GB dynamically allocated, of which 6 GB is effectively in use by a Linux OS => +- 6 GB will be the size on your actual drive

On the internet you can find some statements of people mentioning that dynamically allocated virtual drives tend to be a bit slower than fixed size drives. I felt challenged to find out if that’s actually true! So I went ahead and did some tests to see that if in my case, there is a significant difference in benchmark speed.