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.

Bug 1202788

Summary:	There is no error prompt when set the io throttling parameters FOO_max without FOO and iops_size without iops
Product:	Red Hat Enterprise Linux 7	Reporter:	Gu Nini <ngu>
Component:	qemu-kvm-rhev	Assignee:	Stefan Hajnoczi <stefanha>
Status:	CLOSED ERRATA	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.2	CC:	hannsj_uhl, hhuang, huding, juzhang, michen, qzhang, stefanha, virt-maint, xfu, xuhan, ypu, zhengtli
Target Milestone:	rc
Target Release:	7.3
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	qemu-kvm-rhev-2.5.0-1.el7	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-11-07 20:20:01 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1342330, 1359843

Description Gu Nini 2015-03-17 12:51:38 UTC

Description of problem:
When boot up a guest in qemu cmd with the FOO_max while no the corresponding FOO(such as with bps_max while without bps), the guest could boot up and there is no error prompt, but the FOO_max takes no effect; and after the guest boot up, when set the FOO_max without FOO in qmp, it can be a success and the FOO_max also takes no effect. And there is the same problem on iops_size(while no iops).

Version-Release number of selected component (if applicable):
Host kernel: 3.10.0-229.el7.ppc64
Guest kernel: 3.10.0-229.el7.pc64/3.10.0-229.ael7b.ppc64le
Qemu-kvm-rhev:
qemu-kvm-common-rhev-2.2.0-5.el7.ppc64
qemu-kvm-tools-rhev-2.2.0-5.el7.ppc64
qemu-img-rhev-2.2.0-5.el7.ppc64
ipxe-roms-qemu-20130517-6.gitc4bce43.el7.noarch
qemu-kvm-rhev-2.2.0-5.el7.ppc64
qemu-kvm-rhev-debuginfo-2.2.0-5.el7.ppc64

How reproducible:
100%

Steps to Reproduce:
Please refer to case https://tcms.engineering.redhat.com/case/469227/?from_plan=15759

Actual results:


Expected results:


Additional info:

Comment 2 Xiaoqing Wei 2015-08-10 02:59:23 UTC

met this on x86_64
qemu-kvm-rhev-2.3.0-15.el7.x86_64

and C#0 using ppc, change hardware field to all

Comment 3 Stefan Hajnoczi 2015-09-08 09:40:01 UTC

Deferring to RHEL 7.3.  We have a fix upstream but this bug is not critical (blocker/exception).  This is a QEMU command-line issue which libvirt users will not see.

Comment 5 Stefan Hajnoczi 2016-01-29 14:01:19 UTC

Fixed in upstream version QEMU 2.5.

Comment 7 Gu Nini 2016-05-20 07:01:57 UTC

Stefan,

I have done some test on latest qemu-kvm-rhev version of rhel7.3, it's found the 'FOO_max without FOO' issue is fixed well, while the 'iops_size without iops' one is not. Should it be fixed in rhel7.3? If so, the bug should be reopened.


Thanks!
Nini Gu

Comment 8 Stefan Hajnoczi 2016-06-02 00:27:06 UTC

(In reply to Gu Nini from comment #7)
> I have done some test on latest qemu-kvm-rhev version of rhel7.3, it's found
> the 'FOO_max without FOO' issue is fixed well, while the 'iops_size without
> iops' one is not. Should it be fixed in rhel7.3? If so, the bug should be
> reopened.

Let's make iops_size a separate BZ.  Upstream QEMU does not check that iops/iops_rd/iops_wr has been set if iops_size is used.  A new patch will be required.

Comment 9 Gu Nini 2016-06-03 02:03:25 UTC

(In reply to Stefan Hajnoczi from comment #8)
> 
> Let's make iops_size a separate BZ.  Upstream QEMU does not check that
> iops/iops_rd/iops_wr has been set if iops_size is used.  A new patch will be
> required.

Report bz 1342330 for the iops_size one. And verify this bug on qemu-kvm-rhev-2.6.0-4.el7.x86_64.

Comment 11 errata-xmlrpc 2016-11-07 20:20:01 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-2673.html