the real name of the file doesn't matter if you keep the .conf at the end
this is only for you to remember what it does
as pve-blacklist.conf might be provided by "proxmox package", I would use a
gpu-passthrough-blacklist.conf to keep proxmox able to update his own file and keep mine separate...
I don't know if it is expected or related to my hardware no having a 'rom bar' to get mapped
but this is NOT what I have on my system.
on MY system :
rombar=0 hide my proxmox boot logo and system only show at "login screen"
rombar=1 show me proxmox boot/bios logo and progress bar, then GRUB...
Thanks for this info,
as per rombar=0/1 :
0 mean you wont see bootscreen until OS is ready, thus hidding proxmox boot logo
1 mean you want to see proxmox bootlog to know your VM is firing up
yep, i may give a trial this way first
Worked fine here with linux Guest (my windows ISO won't boot in EFI mode)
exactly as you have done, but this line
without the efifboot=off
vm config file added
bios: ovmf #(from GUI, select BIOS = OVMF)
machine: q35 #(from CLI)