The debug argument for run_bm allows for running curtin outside of the
integration test itself, but with all the setup being done for you by
the integration test. This means that custom tweaks can be done to the
curtin code before running, setting breakpoints, etc.
On plucky, a 20MiB keystore does not allow the install to complete. For some
reason, cryptsetup seems to place the data segment at offset 32MiB instead of
16MiB (which was the case previously).
This results in warnings & errors:
When running crtypsetup luksFormat:
> Device /dev/zvol/rpool/keystore is too small for activation, there is no remaining space for data.
When runnign cryptsetup open:
> Requested offset is beyond real size of device /dev/zvol/rpool/keystore
initramfs config sounds more specific than what this really does. Now,
this runs kernel postinstall hooks for Debian-like systems, providing
the updated initrd functionality along with other expected behaviors.
