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.

+++ This bug was initially created as a clone of Bug #1191428 +++

Description of problem:
To fully replace individual APIs with bulk stats in oVirt, we just lack an equivalent of virDomainGetSchedulerParameters()


Version-Release number of selected component (if applicable):
1.2.12


How reproducible:
100%


Actual results:
No way to get scheduler parameters from bulk stats


Expected results:
new bulk stats group to fetch these stats.


Additional info:
I have a patch in the workings to address this issue, will post for review ASAP

--- Additional comment from Francesco Romani on 2015-02-11 10:32:17 EST ---

Patch posted for review

https://www.redhat.com/archives/libvir-list/2015-February/msg00367.html

Libvirt already has an event that is called when the tunables change from libvirt's point of view.

Adding information that depend on the configured state doesn't go well with the semantics of the bulk stats api as configuration actually doesn't represent any statistics.

I'm closing this as a duplicate of the bug that introduced the cpu tunables event as that is enough to get the required data.

*** This bug has been marked as a duplicate of bug 1115898 ***