GRUB local boot chainloads the disk's signed loader; image sums
On the Secure Boot lab VM, GRUB's "exit" back to the firmware did not reach the disk: OVMF went on to its other network boot options and stopped in its own boot menu. The local-disk entry now finds the installed OS's signed loader on the EFI partition (shimx64.efi under EFI/debian, ubuntu, rocky, almalinux, redhat, centos; shim.efi for SUSE; else EFI/BOOT/BOOTX64.EFI) and chainloads it, as MAAS does. build-image.sh writes SHA256SUMS next to the image (the old one was stale after a rebuild; bootstrap.sh --image-url checks it). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
a0df7295ea
commit
c494c7b226
3 files changed
+24
-3
No files matched your search
@@ -125,5 +125,7 @@ for f in vmlinuz initrd.img filesystem.squashfs; do
|
||||
[ -n "$src" ] || { echo "missing $f in binary/live" >&2; exit 1; }
|
||||
install -m 0644 "$src" "$OUT/$f"
|
||||
done
|
||||
# checked by bootstrap.sh --image-url when another region copies this one
|
||||
(cd "$OUT" && sha256sum vmlinuz initrd.img filesystem.squashfs > SHA256SUMS)
|
||||
ls -la "$OUT"
|
||||
echo "=== done $(date)"
|
||||
Reference in new issue
Block a user