Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
when add bps twice for a dirve in command line, qemu-kvm will give hint :
Block format 'raw' used by device 'disk1' doesn't support the option 'bps'.
This hint is very strange. BTW, test other parameters, such as add "format=raw" twice, it will boot as normal and the second setting is effective.
# /usr/libexec/qemu-kvm -m 2G -smp 2 \
-drive file=/home/RHEL-Server-7.0-64-virtio.qcow2,if=none,media='disk',id=drive-ide0-1-0,readonly=off,format='qcow2',bps=0,format=qcow2,format=qcow2 \
-device virtio-blk-pci,drive=drive-ide0-1-0,id=sys-img \
-monitor stdio -spice port=5932,disable-ticketing -qmp tcp::8888,server,nowait -boot menu=on
Version-Release number of selected component (if applicable):
qemu-kvm-rhev-2.1.0-4.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1. boot guest with setting "bps=0" twice.
# /usr/libexec/qemu-kvm -m 2G -smp 2 -drive file=/home/RHEL-Server-7.0-64-virtio.qcow2,if=none,media='disk',id=drive-ide0-1-0,readonly=off,format='qcow2',bps=0,bps=0 -device virtio-blk-pci,drive=drive-ide0-1-0,id=sys-img -monitor stdio -spice port=5932,disable-ticketing -qmp tcp::8888,server,nowait -boot menu=on
2.
3.
Actual results:
After step 1, qemu-kvm will give hint as followings:
qemu-kvm: -drive file=/home/RHEL-Server-7.0-64-virtio.qcow2,if=none,media=disk,id=drive-ide0-1-0,readonly=off,format=qcow2,bps=0,bps=0: could not open disk image /home/RHEL-Server-7.0-64-virtio.qcow2: Block format 'qcow2' used by device 'drive-ide0-1-0' doesn't support the option 'bps'
Expected results:
qemu-kvm should not give hint "doesn't support the option 'bps'".
Additional info:
Since RHEL7 supports QEMU via libvirt, this shouldn't affect users, so I'm closing this bug.
(please correct me if you can reproduce it via standard libvirt calls).