EFI partitions will never work when held within a Logical Volume via LVM. By selecting advanced partitioning you acknowledge that you understand that things may not work if you make a mistake. EFI partition is part of the UEFI specification which dictates that it be a partition on a GPT disk. By putting it inside an LV you hid it from the UEFI and thus could not boot from it. The startup.nsh file mentioned in the UEFI command-line mode is unrelated. The proper fix in your case is to ensure that the EFI partition is an actual partition and not an LV, and then to perform the install. When this is done the installer will add an entry into the UEFI variables table which indicates which file to use for the boot loader (i.e. grubx64.efi or shimx64.efi depending on whether the UEFI implementation is requiring secure-boot signed files).
On Sun, 26 Jun 2016 at 18:53 PGNet Dev <[email protected]> wrote: > The boot-to-UEFI fail issue's due to a missing 'startup.nsh'. > > It does not appear that it's created during the install process. > > The fix is straightforward, if not quite enduser-friendly. > > After installer stage is complete, destroy, do not reboot, the Guest. > > @ Dom0 host's shell, mount/edit the EFI partition > > kpartx -av /dev/VG0/part_EFI > mount /dev/mapper/VG0-part_EFI1 /mnt > echo "\EFI\ubuntu\grubx64.efi" > /mnt/startup.nsh > umount /mnt > kpartx -dv /dev/VG0/part_EFI > > then reboot. Guest boots successfully to EFI as intended. > > In my book, an installer bug. But I don't know if that's by design > @Ubuntu. > > -- > ubuntu-server mailing list > [email protected] > https://lists.ubuntu.com/mailman/listinfo/ubuntu-server > More info: https://wiki.ubuntu.com/ServerTeam >
-- ubuntu-server mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
