<html> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type"> </head> <body text="#000000" bgcolor="#FFFFFF"> I should add that I am running under CentOS 7.3 with kernel version 3.10.0-514.6.2. <div class="moz-cite-prefix">On 04/27/2017 01:40 PM, Peter Steele wrote: </div> <blockquote cite="mid:59025749.7050102@gmail.com" type="cite"> <meta http-equiv="content-type" content="text/html; charset=utf-8"> I need a container that supports real time threads. According to the documentation, I can do something like this: <domain type='lxc'> <name>test1</name> <uuid>e7446f55-3d59-4af0-90b2-d1498ac4370d</uuid> ... <vcpu placement='auto'>2</vcpu> <cputune> <vcpusched vcpus='0-1' scheduler='fifo' priority='1'/> </cputune> ... </domain> The document describes the vcpusched element as follows: The optional <code>vcpusched</code> elements specifies the scheduler type (values <code>batch</code>, <code>idle</code>, <code>fifo</code>, <code>rr</code>) for particular vCPU/IOThread threads (based on <code>vcpus</code> and <code>iothreads</code>, leaving out <code>vcpus</code>/<code>iothreads</code> sets the default). Valid <code>vcpus</code> values start at 0 through one less than the number of vCPU's defined for the domain. Valid <code>iothreads</code> values are described in the <code>iothreadids</code> <a moz-do-not-send="true" href="https://libvirt.org/formatdomain.html#elementsIOThreadsAllocation" shape="rect"><code>description</code></a>. If no <code>iothreadids</code> are defined, then libvirt numbers IOThreads from 1 to the number of <code>iothreads</code> available for the domain. For real-time schedulers (<code>fifo</code>, <code>rr</code>), priority must be specified as well (and is ignored for non-real-time ones). The value range for the priority depends on the host kernel (usually 1-99). So I *think* my xml is correct for this, but it doesn't seem to work--I still can't create real time threads in my container. Am I missing another configuration step somewhere? Peter </blockquote> </body> </html>