Steps to reproduce:
1) virt-install --connect qemu:///session --name  baremetal_template_debian_buster_uefi --ram 2048 --disk size=4,path=baremetal_template_debian_buster_uefi.img,format=raw,bus=scsi,discard=unmap,cache=unsafe --controller type=scsi,model=virtio-scsi --location http://deb.debian.org/debian/dists/buster/main/installer-amd64/ --os-variant debian10 --virt-type kvm --network user,model=virtio --controller usb,model=none --graphics none --transient --boot uefi --extra-args auto=true hostname=debian domain= console=ttyS0,115200n8 serial net.ifnames=0 variant=buster

Expected results:
1) Debian installer starts

Actual results:
1) the following is printed:

Running text console command: virsh --connect qemu:///session console baremetal_template_debian_buster_uefi
Connected to domain 'baremetal_template_debian_buster_uefi'
Escape character is ^] (Ctrl + ])
!!!! X64 Exception Type - 06(#UD - Invalid Opcode)  CPU Apic ID - 00000000
!!!!
RIP  - 0000000000030000, CS  - 0000000000000038, RFLAGS - 0000000000010246
RAX  - 0000000000000000, RCX - 0000000000000000, RDX - 0000000000000000
RBX  - FFFFFFFFFFFFFFFF, RSP - 000000007EFB7E28, RBP - 000000007EFB7E98
RSI  - 000000007E8EC798, RDI - 000000007EFCCF38
R8   - 0000000000000000, R9  - 0000000003041001, R10 - 000000000000003A
R11  - 000000007E8E9678, R12 - 000000007E8E9018, R13 - 0000000000000001
R14  - 000000008000F880, R15 - 000000008000F844
DS   - 0000000000000030, ES  - 0000000000000030, FS  - 0000000000000030
GS   - 0000000000000030, SS  - 0000000000000030
CR0  - 0000000080010033, CR2 - 0000000000000000, CR3 - 000000007EC01000
CR4  - 0000000000000668, CR8 - 0000000000000000
DR0  - 0000000000000000, DR1 - 0000000000000000, DR2 - 0000000000000000
DR3  - 0000000000000000, DR6 - 00000000FFFF0FF0, DR7 - 0000000000000400
GDTR - 000000007E9EDA98 0000000000000047, LDTR - 0000000000000000
IDTR - 000000007E522018 0000000000000FFF,   TR - 0000000000000000
FXSAVE_STATE - 000000007EFB7A80
!!!! Can't find image information. !!!!

I am guessing this is related to ovmf as the problem does not occur if
I downgrade ovmf to 2020.05-3~bpo+1.