Hello, you're starting to get the idea. Not dumb at al either, it took me a while to figure out and you're right in your post it is NOT documented at all and very vague that they are only talking about LEGACY system passthrough in any post. You want to point proxmox to the disk by ID which you get from:
"find /dev/disk/by-id/ -type l|xargs -I{} ls -l {}|grep -v -E '[0-9]$' |sort -k11|cut -d' ' -f9,10,11,12"
on the proxmox server root shell.
Say for example we were working with: "ata-SPCC_Solid_State_Disk_AA230418S301KG01281"
We set that to "scsiX" to the disk by id so it's using the whole disk not individual partitions then use VirtIO as controller also sometimes it can help to NOT "pre-enroll" the EFI keys (not always but from experience, some EFI VMs don't seem to work with that option)
Then set the CD/ROM to any live linux image I think I used Ubuntu? Then yes follow what you posted and it should set the EFI keys updated to those established in the VM creation process. From there it should work? If I can remember correctly, I actually don't have that VM anymore but if you have any issues please let me know and I will work to help you resolve them
Hmm upon trying to do a sudo mount of the EFI volumen on the second mount cmd, I get an error below, I also find it curious that after the first mount on /mnt, I didn't have the /mnt/boot/efi, but I had a /mnt/efi, I tried to mount the EFI volumen in both places at the error was the same. There is a type of file system that someone is missing....
--- error on second mount cmd ----START
>sudo mount /dev/sdXX /mnt/boot/efi
NTFS signature is missing.
Failed to mount '/dev/sda1': Invalid argument
The device '/dev/sda1' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a partition ....
--- error on second mount cmd ---- END