RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
qemu-kvm ignores virtio-scsi cdrom as a boot device

Version-Release number of selected component (if applicable):
qemu-kvm-1.5.3-19.el7.x86_64
seavgabios-bin-1.7.2.2-4.el7.noarch
seabios-bin-1.7.2.2-4.el7.noarch
sgabios-bin-0.20110622svn-3.el7.noarch

How reproducible:
always

Steps to Reproduce:
1. define libvirt domain with virtio-scsi cdrom such as:
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/path/to/image.iso'/>
      <target dev='sdb' bus='scsi'/>
      <readonly/>
    </disk>
2. define either <boot order='$INT'/> element within disk element or <boot dev='cdrom'/> within <os> element
3. boot the VM

Actual results:
boot from cdrom is not mentioned, when I enable bootmenu, it doesn't show up there

Expected results:
VM boots from virtio-scsi disk

Additional info:

when I delete <address> element and modify the bus parameter to bus='ide', the VM boots just fine...