Comment 5 for bug 2040449

not quite useless if you set hw:mem_encryption then you need to separately set hw_firmware_type in the image

historically configuration of the emulatated devices in a VM was only supported in the image
that also include which fireware interface bios or uefi is presented to the guest.

we could extend that to the flavor but the separation of image vs flavour has been
flavor is for qunatitive elements and image is for qulaitivate.

i can see a use case where an admin wants to create a uefi flavor but the other reason for not doing that in the past is it can only be used with a uefi capable image.
i.e. an image with a gpt portion table and an efi portion
that is why we have used the image to hold the annotation that declares it support uefi not the flavor.