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 of problem:
After cgconfig service restarted and libvirtd restarted ,could not create snapshot for vm.

Version-Release number of selected component (if applicable):
# uname -r
2.6.32-358.6.1.el6.x86_64
# rpm -q libvirt
libvirt-0.10.2-18.el6_4.4.x86_64
# rpm -q qemu-kvm-rhev
qemu-kvm-rhev-0.12.1.2-2.355.el6.3.x86_64


How reproducible:
100%

Steps to Reproduce:
1.service cgconfig restart
2.service libvirtd restart
3.virsh snapshot-create-as testvm s1 --disk-only
  
Actual results:
error: internal error Unable to find cgroup for cho2013051600036
in libvirtd.log:
2013-05-16 02:53:02.062+0000: 16157: error : qemuDomainSnapshotCreateDiskActive:11299 : internal error Unable to find cgroup for testvm
in /cgroup there no cgroup config for testvm.

Expected results:
create snapshot success.

Additional info:

cho2013051600036 is another vm's name ,the error message is:
error: internal error Unable to find cgroup for testvm

I don't think restarting cgconfig service is something we want to support unless there's a real reason for doing that. If you restart cgconfig service, all cgroups are removed and all tasks are moved to the root cgroup.

I'm closing this as not a bug, but feel free to reopen if there is a real situation in which cgconfig service needs to be restarted.

If anything this is really broken behaviour of cgconfig. Nothing should ever unilaterally delete the cgroups hierarchy once the system has booted.