search for: rt_runtime_us

When I create a VM using libvirt, the VM comes up the path /sys/fs/cgroup/cpu/cpu.rt_runtime_us set to something like 1000000. When I create a container however, the path /sys/fs/cgroup/cpu/cpu.rt_runtime_us is 0. This prevents my containers from being able to run any real time applications. I have to explicitly echo a value into this field in order to give the container some real time b...

Hi I was asking about the fedora 14 kernel if it is good enough for cgroup usage because I am trying to set a cgroup under cpu subsytem ( /dev/cgroup/cpu/group1/ ) that have /cpu.rt_runtime_us of 100000 while cpu.rt_period_us has a value of 1000000 i.e a ratio of 1/10 . still when I run a task (endless loop) in that group (cgexec -g cpu,cpuset:group1 ./test) it gets all the cpu core time that is assigned to it ( i watch via top utility) , so it seems that the quota set via the group...

...CentOS 7 : ls /sys/fs/cgroup/cpuacct/machine.slice/machine-qemu\\x2drhel6.0.scope/vcpu0 cgroup.clone_children cgroup.procs cpuacct.usage cpu.cfs_period_us cpu.rt_period_us cpu.shares notify_on_release cgroup.event_control cpuacct.stat cpuacct.usage_percpu cpu.cfs_quota_us cpu.rt_runtime_us cpu.stat tasks ]# RHEL6 : ls /cgroup/cpuacct/libvirt/qemu/VM_Orion-1/vcpu0 cgroup.event_control cgroup.procs cpuacct.stat cpuacct.usage cpuacct.usage_percpu notify_on_release tasks 1) May I assume that their meanings is identical ? 2) Is this difference due to the O.S. or...

We've been using libvirt based containers under CentOS 7 and everything has been working fine. One application we run in our containers is ctdb, which uses SCHED_FIFO (real time) threads. This has been working without problems until our recent upgrade to CentOS 7.3. For some reason, ctdb is no longer able to create real time threads, and I've tried a simple program myself that

...host ~]# virsh start r04s14 error: Failed to start domain r04s14 error: Unable to create cgroup for r04s14: No such file or directory [root at virthost ~]# find /cgroup | grep r04s14 /cgroup/cpu/libvirt/qemu/r04s14 /cgroup/cpu/libvirt/qemu/r04s14/cpu.rt_period_us /cgroup/cpu/libvirt/qemu/r04s14/cpu.rt_runtime_us /cgroup/cpu/libvirt/qemu/r04s14/cpu.stat /cgroup/cpu/libvirt/qemu/r04s14/cpu.cfs_period_us /cgroup/cpu/libvirt/qemu/r04s14/cpu.cfs_quota_us /cgroup/cpu/libvirt/qemu/r04s14/cpu.shares /cgroup/cpu/libvirt/qemu/r04s14/cgroup.event_control /cgroup/cpu/libvirt/qemu/r04s14/notify_on_release /cgroup/cpu/l...

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