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
For non-root user, when executing commands "virsh blkiotune <domainVM>" or "virsh schedinfo <domainVM>", error will occurs but error message is not clear.
Version:
virt-manager-0.10.0-4.el7.noarch
libvirt-1.1.1-9.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Issue the following command to create a user and set its password:
#useradd non-root ; passwd non-root
2. Switch to user "non-root" by command "su - non-root", and create or import a VM named "DomainU1"
3. Execute commands "blkiotune" or "schedinfo" under "non-root" user, and error will occurs.
Actual results:
1. [non-root@localhost ~]$ virsh blkiotune DomainU1
error: Unable to get blkio parameters
error: Requested operation is not valid: blkio cgroup isn't mounted
2. [non-root@localhost ~]$ virsh schedinfo DomainU1
Scheduler : Unknown
error: Requested operation is not valid: cgroup CPU controller is not mounted
The above error message is not clear.
Expected results:
Error message should be clear and improved.
Additional info:
This issue occurs both on RHEL7 and RHEL6.5
Comment 1Martin Kletzander
2014-02-26 17:22:39 UTC
Command "memtune" will have the same problem. These cannot be supported in session mode, so there should be proper error message printed out, working on that.
Comment 2Martin Kletzander
2014-03-06 14:51:31 UTC
Fixed upstream with commit v1.2.2-48-g45ad1ad:
commit 45ad1adb4a5ae5ce46287c570e87abab6ffe62d6
Author: Martin Kletzander <mkletzan>
Date: Thu Feb 27 13:10:32 2014 +0100
qemu: Reject unsupported tuning in session mode
I can produce this bug on
libvirt-1.1.1-9.el7.x86_64
qemu-kvm-rhev-2.1.0-5.el7.x86_64
verify it on
libvirt-1.2.8-8.el7.x86_64
qemu-kvm-rhev-2.1.2-12.el7.x86_64
kernel-3.10.0-208.el7.x86_64
verify steps:
1. create a non-root user test
#useradd test
#passwd test
#su - test
2. prepare a guest under non-root user and start it normaly
$ virsh list --all
Id Name State
----------------------------------------------------
3 aaa running
3. run blkiotune ,schedinfo and memtunewith guest running, shutoff , paused. report error correct
$ virsh blkiotune aaa
error: Unable to get number of blkio parameters
error: unsupported configuration: Block I/O tuning is not available in session mode
$ virsh schedinfo aaa
Scheduler : Unknown
error: Operation not supported: CPU tuning is not available in session mode
$ virsh memtune aaa
error: Unable to get number of memory parameters
error: Operation not supported: Memory tuning is not available in session mode
move to verified
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/RHSA-2015-0323.html