Description of problem: I'm attempting to create a VM using Q35/OVMF and a qcow2 image as VirtIO-SCSI. When this VM boots, I can install a Fedora 30 guest into it. When it reboots, OVMF can't see the Virtio-SCSI device, and displays an error message that it cannot boot. If I change the type of the block device to "VirtIO", it boots successfully. Version-Release number of selected component (if applicable): edk2-ovmf-20190501stable-2.fc30.noarch qemu-3.1.1-2.fc30.x86_64 qemu-common-3.1.1-2.fc30.x86_64 qemu-guest-agent-3.1.1-2.fc30.x86_64 qemu-img-3.1.1-2.fc30.x86_64 qemu-kvm-3.1.1-2.fc30.x86_64 qemu-kvm-core-3.1.1-2.fc30.x86_64 How reproducible: 100% Steps to Reproduce: 1. Install a fresh Fedora 30 Server on hardware. 2. dnf install @virtualization 3. virt-install --name f30_test --memory 2048 --vcpus 1 --pxe --os-type=Linux --os-variant=fedora30 --disk path=/var/lib/libvirt/images/f30_test.img,bus=scsi,size=20 --network bridge:br0 --boot uefi 4. Install Fedora 30 Server, defaults 5. Reboot Actual results: Guest doesn't boot. OVMF can't find the bootloader (or the disk, if you press F2 to go into OVMF's interface). Says "BdsDxe: failed to load Boot0004 "Fedora" from HD0(1,GPT,GUID,0x800,0x64000)/\EFI\fedora\shimx64.efi: Not Found". Expected results: Guest should boot. Additional info: If you change the type of the disk in the VM to Virtio, it will boot. Which means the image exists, was installed, and is good. OVMF just can't see it if the device is VirtIO-SCSI.
Note: both in the steps to reproduce above, and in all of the tests below, I also did a "dnf update". On older hosts, I needed to add --machine q35 to the virt-install line. I tried the same process, but using CentOS 8.0 as the VM host (dnf install @virt). The resulting guest _could_ boot. I tried the same process, but using CentOS 7.7 as the VM host (yum groupinstall "Virtualization Host" / yum install OVMF). To get q35 to work, you have to use the CentOS Virt SIG: "yum install centos-release-qemu-ev / yum install qemu-kvm". The resulting guest _could_ boot. I tried the same process, but using Fedora 29 Server as the VM Host. The resulting guest _could not_ boot. I tried the same process, but using Fedora 28 Server as the VM Host. The resulting guest _could not_ boot. I tried the same process, but using Fedora 27 Server as the VM Host. The resulting guest _could not_ boot. This makes me wonder if I'm doing something wrong, or _not_ doing something. Fedora hosts don't seem to be able to boot UEFI guests with VirtIO SCSI block devices. CentOS 8.0 (and CentOS 7.7 using the CentOS SIG's updated QEMU 2.12) can. Is there something I'm not configuring in Fedora that is needed for this to work?
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '30'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 30 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.