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

Currently, when converting VMs, we've noticed that the firmware type field is missing in the output produced for both -o local and -o kubevirt options. Virt-v2v has the capability to determine the correct type from the disk, even when it's not explicitly specified in the configuration. By posting this output, we can ensure the VM is configured correctly.

Please provide the package NVR for which bug is seen:
virt-v2v-2.3.4-5.el9.x86_64

How reproducible:
100%

Expected results

apiVersion: kubevirt.io/v1
kind: VirtualMachineInstance
metadata:
  name: 1nisim-rhel9-efi
spec:
  domain:
    os:
      firmware: bios/uefi
    devices:
      disks:
      - disk:
          bus: virtio
        name: disk-0
    resources:
      requests:
        memory: 4096Mi
      cpu:
        cores: 2
      features:
  volumes:
  - hostDisk:
      path: /home/nfs/qe/./1nisim-rhel9-efi-sda
      type: Disk
    name: disk-0
  terminationGracePeriodSeconds: 0