Question

9

UEFI boot in virtualbox - Ubuntu 12.04

rated 0 times [ 9] [ 0] / answers: 1 / hits: 15166 / 1 Year ago, fri, december 2, 2022, 8:05:17

I am trying to boot Ubuntu 12.04 (64bit) by using UEFI in VirtualBox. When using UEFI boot in Virtualbox, I instantly get dropped into EFI-shell. I looked this up online and did as explained in this thread. When I do as explained in the thread, I get "efidisk read error". Despite this error, it somehow still boots into Ubuntu, but I end up in tty1.

I have tried this to avoid getting dropped into EFI-shell without any success.

Why does "efidisk read error" appear?

How do I boot directly into Ubuntu without moving to EFI-shell?

How do I get into lightdm from tty1?

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

dersol

Add To Favorites

Follow

Total Points: 78

Total Questions: 100

Total Answers: 124

Location: Christmas Island

Member since Mon, Oct 19, 2020

4 Years ago

dersol questions

1 Horizontal colored lines appearing on display (Ubuntu 22.04)

Wed, Apr 26, 23, 05:00, 1 Year ago

1 /dev/ttyUSB0 not present in Ubuntu 22.04

Mon, May 16, 22, 00:10, 2 Years ago

1 How to write shell script to wget a url once, then wget a second url every two minutes for 1 hour

Sat, Oct 22, 22, 13:45, 2 Years ago

1 zip command keeps including the entire parent directory structure

Tue, Sep 6, 22, 03:26, 2 Years ago

1 Visual Studio Code UI is visually mismatched in Ubuntu 19.10

Sat, May 8, 21, 17:15, 3 Years ago

View All

answered 1 Year ago wheance · Accepted Answer

VirtualBox tends to forget its EFI boot entries. I know of two solutions to this problem:

Move/rename the boot loader you're using (probably EFI/ubuntu/grubx64.efi on the EFI System Partition (ESP)) to EFI/BOOT/bootx64.efi. This is the default/fallback filename, and so VirtualBox will boot from it by default if there are no other entries.

Use the VirtualBox EFI's menus to locate the boot loader you're using (again, probably EFI/ubuntu/grubx64.efi) and add it as a boot option. I don't recall the precise steps, and the menus aren't exactly user-friendly, but if you poke around in the menus, the options are there.

Doing either of these things should get GRUB starting, but then you've got the second issue, of X not starting. To solve this problem, try this:

Do a text-mode login.

Type sudo su to acquire root privileges.

Type Xorg -configure. This should create a file called /root/xorg.conf.new, IIRC.

Copy that newly-create file to /etc/X11/xorg.conf.

Optionally, edit /etc/X11/xorg.conf. This may or may not be required. Personally, I edit the file to set the fbdev driver as the default, but you may prefer something else. There are lots of online guides to xorg.conf, but I don't have any URLs handy, and it can be pretty complex, so completely describing it here is impractical.