managed to build and deploy it,
then i entered rescue mode.
found ESXi partition, which looks like an esp.
$ tree . ├── EFI │ ├── BOOT │ │ └── BOOTx64.EFI │ └── VMware │ ├── mboot64.efi │ └── safebt64.efi ├── ldlinux.sys ├── mboot.c32 ├── root │ ├── curtin-install-cfg.yaml │ └── curtin-install.log ├── safeboot.c32 └── syslinux.cfg
$ md5sum */* | sort 789e1ea8b4df31be58a7f991656a679d BOOT/BOOTx64.EFI 789e1ea8b4df31be58a7f991656a679d VMware/safebt64.efi f88ebb38cf55498e226818a16cd058ce VMware/mboot64.efi
So i'm not sure if we should be booting to mboot64.efi by default; or safebt64.efi (BOOTx64.EFI).
managed to build and deploy it,
then i entered rescue mode.
found ESXi partition, which looks like an esp.
$ tree install- cfg.yaml
.
├── EFI
│ ├── BOOT
│ │ └── BOOTx64.EFI
│ └── VMware
│ ├── mboot64.efi
│ └── safebt64.efi
├── ldlinux.sys
├── mboot.c32
├── root
│ ├── curtin-
│ └── curtin-install.log
├── safeboot.c32
└── syslinux.cfg
$ md5sum */* | sort e58a7f991656a67 9d BOOT/BOOTx64.EFI e58a7f991656a67 9d VMware/safebt64.efi e226818a16cd058 ce VMware/mboot64.efi
789e1ea8b4df31b
789e1ea8b4df31b
f88ebb38cf55498
So i'm not sure if we should be booting to mboot64.efi by default; or safebt64.efi (BOOTx64.EFI).