When virt-v2v converts a guest, it also produces an OVF with configuration based on the inspection of the virtual disk (e.g., driver, firmware, etc). We currently don't look at that, and therefore we missed setting the firmware by what virt-v2v identified. In order to consume this OVF we either need the conversion pod to modify the VM, which is complex, or put the produced OVF in the status of the conversion pod and let forklift-controller process it.

URL: https://github.com/kubev2v/forklift/issues/563