similar to: why CPU pinning doesn't take effect when using lxc-enter-namespace to run an application

On Mon, Dec 22, 2014 at 08:40:03AM +0000, WANG Cheng D wrote: >Dear all, > >I want my container to run on the third CPU core and I define this by the following xml scrpits: ><vcpu placement="static" cpuset="3">1</vcpu> > >When I run my application in a container terminal, I can see the application runs on the third core as expected. >When I run

Hi, Daniel. It seems that the virsh command 'lxc-enter-namespace' encapsulates several functions just as 'virDomainLxcOpenNamespace', 'virDomainGetSecurityLabel', 'virDomainLxcEnterSecurityLabel' , 'virDomainLxcEnterNamespace', 'virFork', etc. And I found only 'virDomainLxcOpenNamespace' is provided by python package 'libvirtmod_lxc

Hello The latest attempts that I made on fedora21 all gave me the same result I have tried . vanilla rpm from f21 (1.2.9 IIRC) . 1.2.14 . 1.2.13 . 1.2.12 these three ones I rebuilt from the source rpm published by libvirt eventually I reworked my own tools to enter the container via ssh, so this is not an immediate concern to me any longer but it is definitely odd I currently use 1.2.12

Hi experts, When I test lxc-enter-namespace interface, it turned out such an error: hzguanqiang@debian:~$ vir version Compiled against library: libvirt 1.1.4 Using library: libvirt 1.1.4 Using API: LXC 1.1.4 Running hypervisor: LXC 3.9.6 hzguanqiang@debian:~$ vir list Id Name State ---------------------------------------------------- 1544 instance-00000015

Hi folks I have a question about lxc-enter-namespace I am migrating lxc containers from a host running libvirt-1.2.5 on f20 to another one running libvirt-1.2.9 on f21 and now I can't seem to use lxc-enter-namespace for entering in a container any more I would do virsh -c lxc:/// lxc-enter-namespace --noseclabel container /bin/bash but when I try the same now I am getting this: # virsh

On 11/14/2013 01:24 PM, Gao feng wrote: > On 11/14/2013 10:59 AM, hzguanqiang@corp.netease.com wrote: >> Hi experts, >> >> When I test lxc-enter-namespace interface, it turned out such an error: >> >> hzguanqiang@debian:~$ <mailto:hzguanqiang@debian:~$> vir version >> Compiled against library: libvirt 1.1.4 >> Using library: libvirt 1.1.4

Hi folks! i created a server with this XML file: <domain type='lxc'> <name>lxctest1</name> <uuid>227bd347-dd1d-4bfd-81e1-01052e91ffe2</uuid> <metadata> <libosinfo:libosinfo xmlns:libosinfo="http://libosinfo.org/xmlns/libvirt/domain/1.0"> <libosinfo:os id="http://centos.org/centos/6.9"/>

Hi Guys, I started a lxc container with libvit in ubuntu Operating system, and succeed using lxc-enter-namespace to enter the namespaces and security context of the container. But when I do the same thing in debian OS, It reported an error, with details as following: root@debian:/etc# vir list Id Name State ---------------------------------------------------- 4424

Dear all I allocate only one vcpu for the container by the following statement, that is, I want to pin the vcpu to physical core "2". <vcpu placement='static' cpuset="2" >1</vcpu> My host has 4 physical cores. Before test, all the 4 cores are idle. After I run 4 processes in the container, I found all the 4 cores in the host are 100% used. That is, the

Hi Gao feng, I noticed one of your patch which adds cpuset cgroup support for lxc have been merged in libvirt 1.0.4. But I can't find any virsh command to set cpusettune for lxc container. Is there anyone? And how can I configure cpusettune for lxc container lively? Thanks ------------------ Best regards! GuanQiang

Hi, I seem to have a problem when creating a LXC container through virsh. While virsh -c lxc:/// dominfo <container> shows up (for example) 2 VCPUs as defined, if I run a CPU intensive task (such as stress --cpu 10) it will max out 10 CPU cores on the host. If I echo "0" > /cgroup/cpuset/libvirt/lxc/<domain>/cpuset.cpus then the container is properly confined to just

On 11/14/2013 01:52 PM, hzguanqiang@corp.netease.com wrote: > On 2013-11-14 13:41 , Gao feng <mailto:gaofeng@cn.fujitsu.com> wrote: > > On 11/14/2013 01:24 PM, Gao feng wrote: > > On 11/14/2013 10:59 AM, hzguanqiang@corp.netease.com wrote: > >> Hi experts, > >> > >> When I test lxc-enter-namespace interface, it turned out such

On 11/14/2013 02:57 PM, hzguanqiang@corp.netease.com wrote: > On 2013-11-14 14:17 , Gao feng <mailto:gaofeng@cn.fujitsu.com> wrote: > > On 11/14/2013 01:52 PM, hzguanqiang@corp.netease.com wrote: > > On 2013-11-14 13:41 , Gao feng <mailto:gaofeng@cn.fujitsu.com> wrote: > > > > On 11/14/2013 01:24 PM, Gao feng wrote: > > >

On 11/14/2013 03:09 PM, hzguanqiang@corp.netease.com wrote: > On 2013-11-14 15:03 , Gao feng <mailto:gaofeng@cn.fujitsu.com> wrote: > > On 11/14/2013 02:57 PM, hzguanqiang@corp.netease.com wrote: > > On 2013-11-14 14:17 , Gao feng <mailto:gaofeng@cn.fujitsu.com> wrote: > > > > On 11/14/2013 01:52 PM, hzguanqiang@corp.netease.com wrote:

Hi, I'm running OpenStack to manage LXC instance through libvirt. The same setting runs perfectly well on Ubuntu 12.04, while on CentOS 6u3, libvirt dumped following message when starting lxc instance. virsh -c lxc:/// start instance-00000032 error: internal error The 'cpuacct', 'devices' & 'memory' cgroups controllers must be mounted Really appreciated if

Hi there, Do you know if there is a way to modify how libvirt interacts with the cgroup? Because, I successfully add the /dev/net/tun support in my LXC container by doing: echo c 10:200 rwm >> /cgroup/libvirt/lxc/instance-00000005/devices.allow But when I restart the instance/LXC container, this option has gone. How can I make this persistant? Is there a configuration file? Thanks

On Tue, Jul 30, 2013 at 05:49:28PM +0800, hzguanqiang wrote: > Hi Guys, > I started a lxc container with libvit in ubuntu Operating system, and succeed using lxc-enter-namespace to enter the namespaces and security context of the container. But when I do the same thing in debian OS, It reported an error, with details as following: > > root@debian:/etc# vir list > Id Name

On Thu, Apr 02, 2015 at 10:25:23AM +0200, Thierry Parmentelat wrote: >Hi folks > >I have a question about lxc-enter-namespace >I am migrating lxc containers from a host running libvirt-1.2.5 on f20 to another one running libvirt-1.2.9 on f21 > >and now I can't seem to use lxc-enter-namespace for entering in a container any more > >I would do >virsh -c lxc:///

How can I run command in containers on the host? Just like the lxc command lxc-attach. I run : virsh -c lxc:/// lxc-enter-namespace fedora2 --noseclabel /bin/ls but get error: libvirt: error : Expected at least one file descriptor error: internal error: Child process (14930) unexpected exit status 125 Here is my libvirt.xml <domain type='lxc'> <name>fedora2</name>

On 2013-11-14 13:41 , Gao feng wrote: On 11/14/2013 01:24 PM, Gao feng wrote: > On 11/14/2013 10:59 AM, hzguanqiang@corp.netease.com wrote: >> Hi experts, >> >> When I test lxc-enter-namespace interface, it turned out such an error: >> >> hzguanqiang@debian:~$ <mailto:hzguanqiang@debian:~$> vir version >> Compiled against library: libvirt 1.1.4