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.
Bug 988261 - qemu prompt that "Parameter 'bps/bps_rd/bps_wr/iops/iops_rd/iops_wr' is missing" is misleading
Summary: qemu prompt that "Parameter 'bps/bps_rd/bps_wr/iops/iops_rd/iops_wr' is missi...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm
Version: 6.5
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Fam Zheng
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 988701
TreeView+ depends on / blocked
 
Reported: 2013-07-25 08:22 UTC by Sibiao Luo
Modified: 2013-09-05 15:31 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 988701 (view as bug list)
Environment:
Last Closed: 2013-09-05 15:31:14 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Sibiao Luo 2013-07-25 08:22:08 UTC 
Description of problem:
boot up guest with data disk, then set io throttle with a big value for it, the qemu will prompt that "Parameter 'bps/bps_rd/bps_wr/iops/iops_rd/iops_wr' is missing" is misleading.

Version-Release number of selected component (if applicable):
host info:
2.6.32-400.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.379.el6.x86_64
seabios-0.6.1.2-28.el6.x86_64
guest info:
2.6.32-400.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1.boot up guest with data disk.
e.g:...-drive file=/home/my-data-disk.qcow2,if=none,id=drive-data-disk,format=qcow2,cache=none,aio=native,werror=stop,rerror=stop,serial="QEMU-DISK2" -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-data-disk,id=data-disk,bootindex=3
2.set io throttle with a big value for it.
(qemu) block_set_io_throttle drive-data-disk 99999999999999999 0 0 0 0 0
(qemu) block_set_io_throttle drive-data-disk 999999999999999999 0 0 0 0 0
(qemu) block_set_io_throttle drive-data-disk 9999999999999999999 0 0 0 0 0
(qemu) block_set_io_throttle drive-data-disk 99999999999999999999 0 0 0 0 0
Parameter 'bps/bps_rd/bps_wr/iops/iops_rd/iops_wr' is missing
(qemu) block_set_io_throttle drive-data-disk 999999999999999999999 0 0 0 0 0
Parameter 'bps/bps_rd/bps_wr/iops/iops_rd/iops_wr' is missing
3.boot guest with qemu i/o throttle (set bps = 99999999999999999999).

Actual results:
after step 2, qemu will prompt that "Parameter 'bps/bps_rd/bps_wr/iops/iops_rd/iops_wr' is missing" is misleading, if set a huge value to throttle the limit will never be hit. 
after step 3, i can boot up successfully, but check the bps=-1 in HMP monitor, if set a huge value to throttle the limit will never be hit, but bps=-1 is also misleading.
(qemu) info block
drive-system-disk: removable=0 io-status=ok file=/home/RHEL6.5-20130721.n.0_6.5_Server_x86_64.qcow2 ro=0 drv=qcow2 encrypted=0 bps=0 bps_rd=0 bps_wr=0 iops=0 iops_rd=0 iops_wr=0
drive-data-disk: removable=0 io-status=ok file=/home/my-data-disk.qcow2 ro=0 drv=qcow2 encrypted=0 bps=-1 bps_rd=0 bps_wr=0 iops=0 iops_rd=0 iops_wr=0

Expected results:
Give a friendly and basically method to deal with it. 

Additional info:
# /usr/libexec/qemu-kvm -S -M rhel6.5.0 -cpu SandyBridge -enable-kvm -m 4096 -smp 4,sockets=2,cores=2,threads=1 -no-kvm-pit-reinjection -name sluo -uuid 43425b70-86e5-4664-bf2c-3b76699b8bec -rtc base=localtime,clock=host,driftfix=slew -device virtio-serial-pci,id=virtio-serial0,max_ports=16,vectors=0,bus=pci.0,addr=0x3 -chardev socket,id=channel1,path=/tmp/helloworld1,server,nowait -device virtserialport,chardev=channel1,name=com.redhat.rhevm.vdsm.1,bus=virtio-serial0.0,id=port1,nr=1 -chardev socket,id=channel2,path=/tmp/helloworld2,server,nowait -device virtserialport,chardev=channel2,name=com.redhat.rhevm.vdsm.2,bus=virtio-serial0.0,id=port2,nr=2 -drive file=/home/RHEL6.5-20130721.n.0_6.5_Server_x86_64.qcow2,if=none,id=drive-system-disk,format=qcow2,cache=none,aio=native,werror=stop,rerror=stop,serial="QEMU-DISK1" -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-system-disk,id=system-disk,bootindex=1 -device virtio-balloon-pci,id=ballooning,bus=pci.0,addr=0x5 -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 -netdev tap,id=hostnet0,vhost=off,script=/etc/qemu-ifup -device virtio-net-pci,netdev=hostnet0,id=virtio-net-pci0,mac=2C:41:38:B6:40:21,bus=pci.0,addr=0x6,bootindex=2 -drive file=/home/my-data-disk.qcow2,if=none,id=drive-data-disk,format=qcow2,cache=none,aio=native,werror=stop,rerror=stop,serial="QEMU-DISK2" -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-data-disk,id=data-disk,bootindex=3 -k en-us -boot menu=on -qmp tcp:0:4444,server,nowait -serial unix:/tmp/ttyS0,server,nowait -vnc :1 -spice port=5931,disable-ticketing -monitor stdio
Comment 1 Sibiao Luo 2013-07-26 03:28:41 UTC 
Also try the QMP monitor:
{"execute":"qmp_capabilities"}
{"return": {}}
{ "execute": "block_set_io_throttle", "arguments": { "device": "drive-data-disk","bps": 99999999999999999999,"bps_rd": 0,"bps_wr": 0,"iops": 0,"iops_rd": 0,"iops_wr": 0 } }
{"return": {}}
{ "execute": "query-block"}
{"return": [...{"io-status": "ok", "device": "drive-data-disk", "locked": false, "removable": false, "inserted": {"iops_rd": 0, "iops_wr": 0, "ro": false, "drv": "raw", "iops": 0, "bps_wr": 0, "encrypted": false, "bps": 9223372036854775807, "bps_rd": 0, "file": "/dev/vg/my-data-disk.raw"}, "type": "unknown"}...]}
(qemu) info block
drive-system-disk: removable=0 io-status=ok file=/dev/vg/system-disk.raw ro=0 drv=raw encrypted=0 bps=0 bps_rd=0 bps_wr=0 iops=0 iops_rd=0 iops_wr=0
drive-data-disk: removable=0 io-status=ok file=/dev/vg/my-data-disk.raw ro=0 drv=raw encrypted=0 bps=9223372036854775807 bps_rd=0 bps_wr=0 iops=0 iops_rd=0 iops_wr=0

But in HMP monitor give a misleading message:
(qemu) block_set_io_throttle drive-data-disk 99999999999999999999 0 0 0 0 0
Parameter 'bps/bps_rd/bps_wr/iops/iops_rd/iops_wr' is missing
Comment 3 Ademar Reis 2013-09-05 15:31:14 UTC 
Closing as wontfix in RHEL6, but leaving rhel7 bug (bug 988701) for further investigation.
Note You need to log in before you can comment on or make changes to this bug.