Kernel not being seen as UEFI stub (I think)

[mounty1]

Your post make me think you did not type in the "efibootmgr -c -d /dev/vda -p 1 -L "Gentoo ...", am I understand correct? if so what generate that command?

No; I did compose and type the command myself. I'll come back with answers to your other points soon.

[mounty1]

Code: Select all

BLK0: Alais(s):
      PciRoot(0x0)/Pci/(0x4,0x0)
BLK1: Alias(s):
      PciRoot(0x0)/Pci/(0x4,0x0)/HD(1,GPT,CAF2DFC5-7494-43A5-99D7-1C412719FC2D,0x800,0x9000)
BLK2: Alias(s):
      PciRoot(0x0)/Pci/(0x5,0x0)
BLK3: Alias(s):
      PciRoot(0x0)/Pci/(0x5,0x0)/HD(1,MBR,0x3391B633,0x800,0x31FF800)
BLK4: Alias(s):
      PciRoot(0x0)/Pci/(0x5,0x1)

I then exercised my little knowledge of the UEFI command shell:

Code: Select all

Shell> BLK1:
Shell> ls
ls: Current directory not specified.
Shell> cd \
cd: Current directory not specified.
Shell>

so for some reason it seems that the EFI partition is not seen by the UEFI software. I don't know where to go from here.

[pingtoo]

Code: Select all

BLK0: Alais(s):
      PciRoot(0x0)/Pci/(0x4,0x0)
BLK1: Alias(s):
      PciRoot(0x0)/Pci/(0x4,0x0)/HD(1,GPT,CAF2DFC5-7494-43A5-99D7-1C412719FC2D,0x800,0x9000)
BLK2: Alias(s):
      PciRoot(0x0)/Pci/(0x5,0x0)
BLK3: Alias(s):
      PciRoot(0x0)/Pci/(0x5,0x0)/HD(1,MBR,0x3391B633,0x800,0x31FF800)
BLK4: Alias(s):
      PciRoot(0x0)/Pci/(0x5,0x1)

I then exercised my little knowledge of the UEFI command shell:

Code: Select all

Shell> BLK1:
Shell> ls
ls: Current directory not specified.
Shell> cd \
cd: Current directory not specified.
Shell>

so for some reason it seems that the EFI partition is not seen by the UEFI software. I don't know where to go from here.

Not even any of FS[0-9]: alias?

No fsX mean nothing on those blkX were understood (as in no recognized file system).

think the blkX as /dev/rdiskX they are block device. you cannot cd into them. they need to be mounted. once mounted fsX will appear. However EFI have no "mount" command, it suppose happen automatically for any supported (by the bhyve implementation) file system. (As far as I can tell UEFI spec mandatory FAT12/16/32)

You can use "map -r" to see if it will cause those fsX appear (I doube that, but it does not hurt to try)

I just realize one thing you /dev/vda may be too small for FAT32, that possible be a reason why EFI did not pick up that partition.