What were you trying to do that didn't work?

When running the v2v with the -o kubevirt I the output file is not fomrated with the kubevirt api and I can't parse the firmware out of the file using the kubevirt api.

What is the impact of this issue to you?

I can't properly parse the file with the CNV api model.

Please provide the package NVR for which the bug is seen:

virt-v2v 2.5.8

How reproducible is this bug?:

Run the v2v with -o kubevirt

Expected results

Have the output which follows the kubevirt api https://kubevirt.io/api-reference/v1.3.1/definitions.html#_v1_firmware

Example
spec:
  template:
    spec:
      domain:
        firmware:
          bootloader: 
            efi:
              persistent: true

Actual results

spec:
  template:
    spec:
      domain:
        os:
          firmware: uefi