diskimage-builder/releasenotes/notes/efi-bootloader-disk-size-4c1a9f18967104fb.yaml

---
fixes:
  - |
    When using the ``block-device-efi`` element to create an EFI based
    system (most notably, with ARM64), the final disk size is now
    expanded for the 512MiB system EFI partition introduced with 2.24.0
block-device-efi : expand disk size calculation As noted in the change, 7fd52ba84180b4e749ccf4c9db8c49eafff46ea8 increased the size of the EFI partition considerably. This has meant that our padding upwards of the disk size is insufficient and EFI builds (arm64 in particular) is failing due to out-of-disk errors during final image operations like installing kernels. Similar to the discussion we had in I65fa13a088eecdfe61636678578577ea2cfb3c0c, this feels a bit ugly because we're mixing logic here with sizes specified in block-device config files. But it boils down to the same problem; we are calculating the disk size here and passing it to the block-layer, so unless we want to make large changes to the status quo about where these sizes are calculated, small adjustments here are the most KISS solution. Thus we check if we have selected the EFI bootloader element, and thus assume there will be a large system EFI partition and expand the disk size accordingly. Change-Id: Ifa05366c2f2b95259f3312e4dde8c85347075ba1 2019-08-14 05:24:03 +00:00			`---`
			`fixes:`
			`- \|`
			When using the ``block-device-efi`` element to create an EFI based
			`system (most notably, with ARM64), the final disk size is now`
			`expanded for the 512MiB system EFI partition introduced with 2.24.0`