[libvirt-users] How to retrieve legacy cgroups location ?
Hi, As told in "Control Groups Resource Management" libvirt page : Legacy cgroups layout Prior to libvirt 1.0.5, the cgroups layout created by libvirt was different from that described above, and did not allow for administrator customization. Libvirt used a fixed, 3-level hierarchy libvirt/{qemu,lxc}/$VMNAME which was rooted at the point in the hierarchy where libvirtd itself was located. So if libvirtd was placed at /system/libvirtd.service by systemd, the groups for each virtual machine / container would be located at /system/libvirtd.service/libvirt/{qemu,lxc}/$VMNAME. In addition to this, the QEMU drivers further child groups for each vCPU thread and the emulator thread(s). This leads to a hierarchy that looked like I'm trying to retrieve this layout : $ROOT | +- system | +- libvirtd.service | +- libvirt | +- qemu | | | +- vm1 | | | | | +- emulator | | +- vcpu0 | | +- vcpu1 | | | +- vm2 | | | | | +- emulator | | +- vcpu0 | | +- vcpu1 | | | +- vm3 | | | +- emulator | +- vcpu0 | +- vcpu1 How may I find where systemd has placed libvirtd ? I use libvirt 0.10.2 on a RHEL6 2.6.32-431.el6.x86_64 Thx for help. J.P. Ribeauville P: +33.(0).1.47.17.20.49 . Puteaux 3 Etage 5 Bureau 4 jpribeauville@axway.com<mailto:jpribeauville@axway.com> http://www.axway.com<http://www.axway.com/> P Pensez à l'environnement avant d'imprimer.
On Thu, Oct 29, 2015 at 10:40:44AM +0000, Jean-Pierre Ribeauville wrote:
Hi,
As told in "Control Groups Resource Management" libvirt page : Legacy cgroups layout Prior to libvirt 1.0.5, the cgroups layout created by libvirt was different from that described above, and did not allow for administrator customization. Libvirt used a fixed, 3-level hierarchy libvirt/{qemu,lxc}/$VMNAME which was rooted at the point in the hierarchy where libvirtd itself was located. So if libvirtd was placed at /system/libvirtd.service by systemd, the groups for each virtual machine / container would be located at /system/libvirtd.service/libvirt/{qemu,lxc}/$VMNAME. In addition to this, the QEMU drivers further child groups for each vCPU thread and the emulator thread(s). This leads to a hierarchy that looked like
I just skimmed through the question, but wouldn't reading '/proc/$(pidof libvirtd)/cgroup' or cat /proc/$QEMU_PID/cgroup be enough?
I'm trying to retrieve this layout :
$ROOT | +- system | +- libvirtd.service | +- libvirt | +- qemu | | | +- vm1 | | | | | +- emulator | | +- vcpu0 | | +- vcpu1 | | | +- vm2 | | | | | +- emulator | | +- vcpu0 | | +- vcpu1 | | | +- vm3 | | | +- emulator | +- vcpu0 | +- vcpu1
How may I find where systemd has placed libvirtd ?
I use libvirt 0.10.2 on a RHEL6 2.6.32-431.el6.x86_64
Thx for help.
J.P. Ribeauville
P: +33.(0).1.47.17.20.49 . Puteaux 3 Etage 5 Bureau 4
jpribeauville@axway.com<mailto:jpribeauville@axway.com> http://www.axway.com<http://www.axway.com/>
P Pensez à l'environnement avant d'imprimer.
_______________________________________________ libvirt-users mailing list libvirt-users@redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users
Hi, 1) As I was totally unable to find it , I tried to reboot my server. 2) And then, I found all the stuff located there (included the three subdirs for the 3 Guests) : ls /cgroup/cpu/libvirt/qemu cgroup.event_control cgroup.procs cpu.cfs_period_us cpu.cfs_quota_us cpu.rt_period_us cpu.rt_runtime_us cpu.shares cpu.stat notify_on_release tasks VM_Orion-1 VM_Orion-2 VM_ORION-W2008R2-1 Thx. J.P. -----Message d'origine----- De : Martin Kletzander [mailto:mkletzan@redhat.com] Envoyé : jeudi 29 octobre 2015 11:54 À : Jean-Pierre Ribeauville Cc : libvirt-users@redhat.com Objet : Re: [libvirt-users] How to retrieve legacy cgroups location ? On Thu, Oct 29, 2015 at 10:40:44AM +0000, Jean-Pierre Ribeauville wrote:
Hi,
As told in "Control Groups Resource Management" libvirt page : Legacy cgroups layout Prior to libvirt 1.0.5, the cgroups layout created by libvirt was different from that described above, and did not allow for administrator customization. Libvirt used a fixed, 3-level hierarchy libvirt/{qemu,lxc}/$VMNAME which was rooted at the point in the hierarchy where libvirtd itself was located. So if libvirtd was placed at /system/libvirtd.service by systemd, the groups for each virtual machine / container would be located at /system/libvirtd.service/libvirt/{qemu,lxc}/$VMNAME. In addition to this, the QEMU drivers further child groups for each vCPU thread and the emulator thread(s). This leads to a hierarchy that looked like
I just skimmed through the question, but wouldn't reading '/proc/$(pidof libvirtd)/cgroup' or cat /proc/$QEMU_PID/cgroup be enough?
I'm trying to retrieve this layout :
$ROOT | +- system | +- libvirtd.service | +- libvirt | +- qemu | | | +- vm1 | | | | | +- emulator | | +- vcpu0 | | +- vcpu1 | | | +- vm2 | | | | | +- emulator | | +- vcpu0 | | +- vcpu1 | | | +- vm3 | | | +- emulator | +- vcpu0 | +- vcpu1
How may I find where systemd has placed libvirtd ?
I use libvirt 0.10.2 on a RHEL6 2.6.32-431.el6.x86_64
Thx for help.
J.P. Ribeauville
P: +33.(0).1.47.17.20.49 . Puteaux 3 Etage 5 Bureau 4
jpribeauville@axway.com<mailto:jpribeauville@axway.com> http://www.axway.com<http://www.axway.com/>
P Pensez à l'environnement avant d'imprimer.
_______________________________________________ libvirt-users mailing list libvirt-users@redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users
participants (2)
-
Jean-Pierre Ribeauville -
Martin Kletzander