similar to: Real time threads don't work in libvirt containers under CentOS 7.3

Hi all, We observed that under certain circumstances pthread_create() (libasan implemention) does not return. The conditions are the following: - address sanitizer enabled - main and child thread run on the same CPU (affinity) - real-time scheduling policy for both threads - different scheduling priority values (this includes the case of setting a real-time policy for one of the threads and

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

>I can't really comment on jackd itself, as I haven't looked that much >into it. If running jackd as root requires client apps to also run as >root then that is a pretty bad issue. I would of thought that running >jackd as a realtime process (whether root or not) would be an important >consideration. jackd (realtime) requires various resources which it shares with its

We're transitioning from a VM based environment to one that uses LXC based containers running under CentOS 7. CTDB runs fine under our CentOS 7 VMs. The same packages running under LXC however seem to have issues: # systemctl start ctdb.service Job for ctdb.service failed. See 'systemctl status ctdb.service' and 'journalctl -xn' for details. # systemctl status ctdb.service

I'm using libvirt_lxc and that has an XML based configuration. Based on what I've read, I think I need to add this to the ctdb container's config: <features> <capabilities policy='default'> <sys_nice state='on'/> </capabilities> </features> That didn't do the trick though. I need to figure out how to turn on all caps to

On 2015-08-04 at 19:27 +0200, Ralph Böhme wrote: > Hi Peter, > > On Tue, Aug 04, 2015 at 10:11:56AM -0700, Peter Steele wrote: > > We're transitioning from a VM based environment to one that uses LXC based > > containers running under CentOS 7. CTDB runs fine under our CentOS 7 VMs. > > The same packages running under LXC however seem to have issues: > > >

Hello, looks like Asterisk (at least the Version 1.4.21.2 from debian lenny, which I use) has a serious Problem with pseudo-realtime mode (-p switch) in conjunction with recent Kernels. Whenn using -p Asterisk simply hangs forever on startup. This is almost certainly related to the CFS SCHED_FIFO changes: http://lwn.net/Articles/296419/ Do you know how a workaround or patch how to run asterisk

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

I'm using libvirt_lxc to create and manage various containers. I need to enable certain capabilities in a container to support ctdb, and as a quick solution I decided to just enable them all. I *thought* this would do the trick, adding the following XML to my container config: <features> <capabilities policy='allow'> </capabilities> </features> After

Fritz just put the first version of a new time series package to the contrib section at CRAN. The package is called "tseries.tgz" and provides a library for time series analysis. It contains acf Autocorrelation Function adf.test Augmented Dickey-Fuller Test amif Auto Mutual Information Function bds.test BDS Test

Fritz just put the first version of a new time series package to the contrib section at CRAN. The package is called "tseries.tgz" and provides a library for time series analysis. It contains acf Autocorrelation Function adf.test Augmented Dickey-Fuller Test amif Auto Mutual Information Function bds.test BDS Test

On Mon, 2004-10-18 at 22:14, Paul Davis wrote: > jackd (realtime) requires various resources which it shares with its > clients: > > realtime scheduling > mlock-ability > shared memory segments > FIFOs (or Mach ports on OS X) > > we consider it *more* of a security risk to allow jackd-as-root to > share these with non-root processes. YMMV.

Karl Heyes <karl@xiph.org> writes: > On Mon, 2004-10-18 at 18:27, Jack O'Quin wrote: > > Karl Heyes <karl@xiph.org> writes: > > > > > Are you running with realtime privileges, for this you need to start as > > > root if you want that. Even with realtime privileges there may be odd > > > cases where the scheduling latency is a bit too

On Mon, Feb 06, 2017 at 09:32:29AM -0800, Peter Steele wrote: > 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

Hi Peter, On Tue, Aug 04, 2015 at 10:11:56AM -0700, Peter Steele wrote: > We're transitioning from a VM based environment to one that uses LXC based > containers running under CentOS 7. CTDB runs fine under our CentOS 7 VMs. > The same packages running under LXC however seem to have issues: > > # systemctl start ctdb.service > Job for ctdb.service failed. See 'systemctl

Hi, My piece of code ( C langage) uses cgroups to retrieve counters related to cpu and memory usage related to KVM guests hosted by the host where this code runs. I noticed that depending on the O.S. running on the host , these counters are not found at the same location : CentOS 7 : ls /sys/fs/cgroup/cpuacct/machine.slice/machine-qemu\\x2drhel6.0.scope/vcpu0 cgroup.clone_children

Hey again, Am 2014-08-19 12:26, schrieb Jonas Meurer: > I encounter kernel crashes on an up-to-date Debian/Wheezy Xen domU with > the > stock kernel. The dom0 runs the same linux kernel and > xen/4.1.4-3+deb7u1. the bug is still reproducible with the latest kernel and Xen packages from Debian Wheezy. Unfortunately it seems like a corner case, somehow related to the hardware

Here's couple of patches to improve the softlockup watchdog. The first changes the softlockup timer from using jiffies to sched_clock() as a timebase. Xen and VMI implement sched_clock() as counting unstolen time, so time stolen by the hypervisor won't cause the watchdog to bite. The second adds per-cpu enable flags for the watchdog timer. This allows the timer to be disabled when the

Here's couple of patches to improve the softlockup watchdog. The first changes the softlockup timer from using jiffies to sched_clock() as a timebase. Xen and VMI implement sched_clock() as counting unstolen time, so time stolen by the hypervisor won't cause the watchdog to bite. The second adds per-cpu enable flags for the watchdog timer. This allows the timer to be disabled when the

Like with the previous commit, this replaces instances of: if (something_bad) { fprintf (stderr, "%s: error message\n", guestfs_int_program_name); exit (EXIT_FAILURE); } with: if (something_bad) error (EXIT_FAILURE, 0, "error message"); (except in a few cases were errno was incorrectly being ignored, in which case I have fixed that). It's slightly