> Unfortunately it's not persistent upon system reboot/reset.

Doesn't reproduce.  It is persistent for me (edk2-ovmf-20220526git16779ede2d36-3.fc36).

It's not persistent for me on a fresh VM created after upgrading to Fedora 36 (to make sure latest edk2 is used): edk2-ovmf-20220526git16779ede2d36-3.fc36.noarch

1. Create entry
2. Check it's in Boot Manager Menu: present
3. Select Reset in main menu
4. Check it's in Boot Manager Menu: not there

Still doesn't reproduce here.  Can add entry.  See it just fine in both firmware setup and booted system (entry 0007 below).

[core@localhost ~]$ efibootmgr -v
BootCurrent: 0007
Timeout: 3 seconds
BootOrder: 0006,0001,0007,0002,0003,0005,0004,0000
Boot0000* UiApp	FvVol(7cb8bdc9-f8eb-4f34-aaea-3ee4af6516a1)/FvFile(462caa21-7614-4503-836e-8ab6f4662331)
Boot0001* UEFI QEMU QEMU HARDDISK 	PciRoot(0x0)/Pci(0x2,0x2)/Pci(0x0,0x0)/SCSI(0,0)N.....YM....R,Y.
Boot0002* UEFI PXEv4 (MAC:525400038C1F)	PciRoot(0x0)/Pci(0x2,0x0)/Pci(0x0,0x0)/MAC(525400038c1f,1)/IPv4(0.0.0.00.0.0.0,0,0)N.....YM....R,Y.
Boot0003* UEFI PXEv6 (MAC:525400038C1F)	PciRoot(0x0)/Pci(0x2,0x0)/Pci(0x0,0x0)/MAC(525400038c1f,1)/IPv6([::]:<->[::]:,0,0)N.....YM....R,Y.
Boot0004* UEFI HTTPv4 (MAC:525400038C1F)	PciRoot(0x0)/Pci(0x2,0x0)/Pci(0x0,0x0)/MAC(525400038c1f,1)/IPv4(0.0.0.00.0.0.0,0,0)/Uri()N.....YM....R,Y.
Boot0005* UEFI HTTPv6 (MAC:525400038C1F)	PciRoot(0x0)/Pci(0x2,0x0)/Pci(0x0,0x0)/MAC(525400038c1f,1)/IPv6([::]:<->[::]:,0,0)/Uri()N.....YM....R,Y.
Boot0006* Fedora	HD(1,GPT,3ab627a8-4d42-4f42-a63f-8cd66d0c1a7b,0x800,0x12c000)/File(\EFI\fedora\shimx64.efi)
Boot0007* coreos	PciRoot(0x0)/Pci(0x2,0x0)/Pci(0x0,0x0)/MAC(525400038c1f,1)/IPv4(0.0.0.00.0.0.0,0,0)/Uri(http://spunk.home.kraxel.org/mirror/fedora/coreos/35.20220424.3.0-x86_64/fedora-coreos-35.20220424.3.0-live.x86_64.iso)

Can you try booting the system before and after reset and inspect settings with efibootmgr?

I reproduce without effectively installing the system, just entering the firmware, creating the entry, checking it's there and resetting the system (not hard resetting, using the entry in the menu).
I chose "UEFI" which ends up using /usr/share/edk2/ovmf/OVMF_CODE.secboot.fd and I'm in Secure Boot as well.

(In reply to Renaud Métrich from comment #4)
> I reproduce without effectively installing the system, just entering the
> firmware, creating the entry, checking it's there and resetting the system
> (not hard resetting, using the entry in the menu).
> I chose "UEFI" which ends up using /usr/share/edk2/ovmf/OVMF_CODE.secboot.fd
> and I'm in Secure Boot as well.

Same here.
Doesn't matter whenever I use an existing guest or create a fresh one.
Doesn't matter whenever I use libvirt or start qemu directly.
Doesn't matter whenever secure boot is active or not.
All working fine here.

This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '35'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.

Fedora Linux 35 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.