3294aecca2
We've noticed that centos8 arm64 images have a root devices of /dev/mapper/loop7p3 which make sense within a dib image build context but not at boot time. Dib intends to use labels to set the root device but when efi is used we end up running grub2-mkconfig against the efi grub config path before we configure grub to use labels. Fix this by running grub2-mkconfig after its configuration is set. This should avoid confusion and complicated paths through the scripts that configure this for us. We then copy the resulting config to the efi specific grub.cfg location for platforms that have it. There is also a small refactoring that is done to try and make the ~3 boot variants more clear: 1) Booting with legacy bios 2) Booting with uefi without a signed shim that directly calls grub 3) Booting with uefi and a signed shim that calls grub Options 1 and 2 share the /boot/grub*/grub.cfg file. Option 3 needs its grub.cfg to live alongside distro specific efi target. Change-Id: Ie9790da9d1bbea58197b37b15a48e77f8a93c1ac |
||
|---|---|---|
| .. | ||
| block_device | ||
| elements | ||
| lib | ||
| tests | ||
| __init__.py | ||
| disk_image_create.py | ||
| element_dependencies.py | ||
| logging_config.py | ||
| paths.py | ||
| version.py | ||