-
Bug
-
Resolution: Unresolved
-
Major
-
rhel-10.0
-
None
-
No
-
Important
-
1
-
rhel-sst-virtualization
-
ssg_virtualization
-
100
-
False
-
-
None
-
zKVM CY24Q4
-
None
-
None
-
-
s390x
-
None
What were you trying to do that didn't work?
The following boot scenarios don't work:
- Boot from a non-bootable CD-ROM image first, then from a hard disk or network device next
- Boot from a non-bootable network device first, then from a bootable network device
- The scsi-hd devices don't have a "loadparm" property yet
Please provide the package NVR for which the bug is seen:
qemu-kvm-9.1.0-4.el10
How reproducible is this bug?
100%
Steps to reproduce
- /usr/libexec/qemu-kvm ... \
-drive if=none,id=d1,file=/tmp/bad.dat,format=raw,media=cdrom \
-device virtio-scsi -device scsi-cd,drive=d1 \
-drive if=none,id=d2,file=good.qcow2 -device virtio-blk,drive=d2 - /usr/libexec/qemu-kvm ... -netdev user,id=n1 \
-device virtio-net-ccw,netdev=n1,bootindex=1 \
-netdev user,id=n2,tftp=/boot,bootfile=vmlinuz \
-device virtio-net-ccw,netdev=n2,bootindex=2 - /usr/libexec/qemu-kvm ... -device scsi-hd,drive=d1,loadparm="1"
Expected results
The guest should be able to boot successfully
Actual results
- clones
-
RHEL-68440 The new "boot order" feature is sometimes not working as expected [RHEL 9]
- Planning