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.
Created attachment 1738146[details]
libvirt xml
Created attachment 1738146[details]
libvirt xml
Description of problem:
Start a vm by virsh, the values of"virsh schedinfo xx --set global_quota/cpu_shares" would change into previous one after systemctl daemon-reload.
I guess that maybe the same reason as Bug1789824.
Version-Release number of selected component (if applicable):
systemd-239-18.el8.x86_64
libvirt-4.5.0.35
How reproducible:
Consistently reproducible
Steps to Reproduce:
1. Start a vm and "virsh schedinfo <domain>"
2. "virsh schedinfo <domain> --set cpu.shares=2048"
3. "virsh schedinfo <domain>"
4. "systemctl daemon-reload"
5. "virsh schedinfo <domain>"
Actual results:
1. start vm successfully, and get an initial value of cpu.shares
2. no error
3. get a value of cpu.shares 2048
4. no error
5. cpu.shares was changed into initial value
Expected results:
1. start vm successfully, and get an initial value of cpu.shares
2. no error
3. get a value of cpu.shares 2048
4. no error
5. cpu.shares is the value newly setted
Additional info:
Im reviewing code of libvirt, It seems that libvirt misuse the Delegate= which was designed to delegate subtree's property to other programs, but not the property of scope/slice performing Delegate=.
I would like to test compling a libvirt that modified functions virCgroupSet*() into call systemctl api to tell systemd.