similar to: an error caused by lxc-enter-namespace command

I'd also like to point out that, when setting up a linux container with _just_ the lxc tools available in ubuntu, all that was needed to be done was whitelist the appropriate cgroups for the Android devices. The lxc tools seem to create the appropriate character devices when you detach/attach the Android device via USB, and the Android `adb` tool recognized the devices. So, a tangential

So, if I remove the hostdev element related to the USB device, running `lsusb` and `usb-devices` inside the container lists the proper device, but I do not see the appropriate character device bus for the Android device under /dev/bus/usb. We are not entirely sure that `lsusb` and `usb-devices` queries the appropriate location - it somehow gets information from the host, not the guest container,

Can you see the USB device in the lxc? My answering assumes you cannot see the USB device in the container. If you can see it, please ignore my answer. According to my understanding, “hostdev mode='subsystem' “ is used with KVM only. We use this if we want to passthrough a device to a KVM virtual machine. After doing that, the host machine will lose control of the device. If container is

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

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 my application using lxc-enter-namespace, the CPU pinning doesn't take effect, i.e.,

Hi, I'm not libvirt expect. My guess is that some vcpu settings only apply to KVM/qemu backend. LXC is quite different from them. If setting vcpu# is not effective for LXC container, you may need to use cgroups. -- Thanks, Yuanle On Mon, Mar 17, 2014 at 2:32 PM, WANG Cheng D < Cheng.d.Wang@alcatel-sbell.com.cn> wrote: > Dear all, > > I am not clear about the

Dear all, I am not clear about the 'vcpu' element for CPU allocation. I allocated 1 vCPU to my container, after I started the container, I ran 4 computation-intensive tasks on the container. And I found all the 4 physical core are 100% used (my host has 4 physical cores and no other application ran on the host except the container). That is, all available cores were used by the container.

Dear Fil, I am not sure if my answer can help you. I had ever asked a similar question to Daniel and I was using a thirty-party card. As a container uses a shared kernel with the host, so hostdev mode='subsystem' doesn't make sense. Maybe you can try to use hostdev mode='capabilities'. Please see http://libvirt.org/formatdomain.html#elementsHostDevCaps Hope this helps Cheng

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

Hi Chang Weng, Thanks for answering! Could you explain why subsystem=USB does not make sense? I was simply following the documentation for USB devices (right above the section you linked to). For what it's worth, I've also tried mounting the specific character device related to the appropriate android device into the container in the way you suggest, with no luck; `adb` still does not

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:///

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 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 2013-11-14 14:17 , Gao feng 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 10:59 AM, hzguanqiang@corp.netease.com wrote: > >> Hi experts, > >> > >> When I test

Hello everyone, referring back to https://www.redhat.com/archives/libvirt-users/2013-August/msg00107.html, in which a user discovered that there is no equivalent to "virsh -c lxc:/// lxc-enter-namespace" in the Python API. Has that ever changed? In that thread Daniel suggested that the user file a bug, but that apparently never happened. Why am I interested in this? Ansible currently

Hello everyone, referring back to https://www.redhat.com/archives/libvirt-users/2013-August/msg00107.html, in which a user discovered that there is no equivalent to "virsh -c lxc:/// lxc-enter-namespace" in the Python API. Has that ever changed? In that thread Daniel suggested that the user file a bug, but that apparently never happened. Why am I interested in this? Ansible currently

On 2013-11-14 15:03 , Gao feng 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: > > On 2013-11-14 13:41 , Gao feng <mailto:gaofeng@cn.fujitsu.com> wrote: > > > > On 11/14/2013 01:24 PM,

On 2013-11-14 16:40 , 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,

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

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