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 683428

Summary:	Inappropriate ioctl for device When set harddisk to low performance status on RHEL 6.1 host
Product:	Red Hat Enterprise Linux 7	Reporter:	Joy Pu <ypu>
Component:	qemu-kvm-rhev	Assignee:	John Snow <jsnow>
Status:	CLOSED WONTFIX	QA Contact:	aihua liang <aliang>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.0	CC:	aliang, amit.shah, areis, juzhang, knoel, kwolf, mkenneth, tburke, virt-maint, xuwei
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	662903	Environment:
Last Closed:	2017-11-16 22:45:48 UTC	Type:	---
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:	662903
Bug Blocks:	580954

Comment 2 Joy Pu 2011-03-09 12:07:39 UTC

Find this problem again in RHEL 6.1 host and RHEL 6.1 guest. And conform with Christoph, and open this bug as his advice.

Comment 10 Xueqiang Wei 2015-04-28 08:43:15 UTC

Hi Kevin,

I reproduce this bug on RHEL6.7 host and RHEL6.7 guest

Host:
kernel-2.6.32-551.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.465.el6.x86_64


If it will be fixed in rhel6?


Thanks
Xueqiang

Comment 11 Kevin Wolf 2015-04-28 13:27:41 UTC

Certainly not in RHEL 6. I'm not sure if it's worth fixing at all because it
doesn't actually provide any additional functionality or fix a real bug. It would
only make the warning go away with no other change in behaviour.

However, as this is IDE, I'm reassigning this to John and let him decide.

Comment 12 John Snow 2015-06-23 23:00:45 UTC

Not likely to be fixed in the immediate future; the SET_FEATURES command is complicated (and mandatory) and even stubbing the responses to the satisfaction of HDParm will probably take a solid week to get right.

I don't think I'll close this bug, but I am going to kick the can down the road for now.

I will investigate fixing this upstream, but it won't hit 7.2.

Comment 15 aihua liang 2017-11-08 07:39:54 UTC

Bug still exit in RHEL7.5
 
 kernel version: 3.10.0-772.el7.x86_64
 qemu-kvm-rhev version:qemu-kvm-rhev-2.10.0-4.el7.x86_64

Comment 16 John Snow 2017-11-16 22:45:48 UTC

Closing this for our downstream version of this package as only a cosmetic problem.

If it is found to actually impair any technical operation, please re-open. Different performance modes in QEMU can be achieved by using throttling and performance settings on the host. We generally don't or will not be respecting requests from the guests to inhibit performance artificially through the IDE layer specifically.

For now, this is WONTFIX. If someone stumbles across this BZ from google and you are finding this bug is preventing you from performing some legitimate action with e.g. HDParm, please file a bug /upstream/ using the launchpad tracker, or reach out to us on the list at qemu-block.

Thanks,
John