lsvmload.efi's assumptions about partition UUIDs or LUKS are undocumented

[Avamander]

After careful artisanal crafting (because the scripts are a bit outdated by now), I've managed to do everything except get lsvmload to unlock a LUKS partition. Even with a manually entered passphrase.

I've tried all four combinations for RootDevice and RootDeviceLUKS values (PARTUUID-UUID, UUID-UUID, PARTUUID-PARTUIID, UUID-PARTUUID). If it's some other UUID then it's not generated or shown by the current lsvmprep utility.

I get the impression that UEFI block IO (BIO) might see something different or the Hyper-V UEFI implementation might, but it's unclear what it might be.

The disk is nicely GPT and the partitions are LUKS v1 (I also tried v2, but that didn't change anything).

Log output:

INFO: progress: Checking boot partition
ERROR: failed to find LUKS BIO for uuid: [[Replace with any UUID or PARTUUID]]
INFO: No LUKS BIO found
ERROR: GetBootDevice() failed
ERROR: failed to open the boot parition