Some UEFI images are not bootable in UEFI mode
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-images |
New
|
Undecided
|
Unassigned |
Bug Description
Recently, changes to various cloud-images (grub2 I believe) has broken booting while in UEFI mode.
It's somewhat complicated to track the versions and files, but hopefully the table included can help track down where the change occurred. For 14.04 and 16.04, I used the -uefi1.img, from 16.10 onward, the .img file is UEFI boot-capable (and a separate -uefi1.img file is not published).
All testing occurred on a Xenial amd64 host.
I'll attach the script used to launch the images in UEFI mode,
The template command, note the cloud-imaige is set up as the
first bootable device (bootindex=0) and we use
pflash devices to load the uefi firmware, one for the readonly
code, and a second writable device to hold any NVRAM changes.
qemu-system-x86_64 -m 1024 --enable-kvm \
-snapshot \
-drive id=disk0,
-device virtio-
-cdrom $SEED \
-net user -net nic,model=virtio \
-redir tcp:22222::22 \
-monitor stdio \
-drive if=pflash,
-drive if=pflash,
-serial telnet:
The following table document what works and what doesnt.
In case this formats poorly, it can also be found here
http://
and will be attached to the bug as well.
#release #Ver #Type #Date #Grub version # Boots? #Comments
trusty 14.04 daily 20170510 2.02~beta2-
xenial 16.04 release 20160420 2.02~beta2-
xenial 16.04 release 20161020 2.02~beta2-
xenial 16.04 release 20170330 2.02~beta2-
xenial 16.04 daily 20170508 2.02~beta2-
xenial 16.04 daily 20170510 2.02~beta2-
yakkety 16.10 release 20161023 2.02~beta2-
yakkety 16.10 daily 20170510 2.02~beta2-
zesty 17.04 release 20170412 2.02~beta3-4ubuntu2 FAILS
zesty 17.04 daily 20170510 2.02~beta3-4ubuntu2 FAILS
artful 17.10 daily 20170510 2.02~beta3-4ubuntu2 WORKS
bash ./cloud.sh <path to image file> <user-data-file>