search for: crwx

Displaying 6 results from an estimated 6 matches for "crwx".

Did you mean: crux
2017 Feb 03
2
accessing USB as storage device through lxc container.
...bling the usb as storage device. Any pointers towards that would be useful. Host OS: IR800-GOS-1:~# lsusb Bus 001 Device 003: ID 8644:800b Bus 001 Device 001: ID 1d6b:0002 Bus 002 Device 001: ID 1d6b:0001 IR800-GOS-1:~# Lxc app container: root@ir800-lxc:/mnt/usb# ls -la /dev/bus/usb/001/003 *crwx-*----- 1 root root 189, 2 Feb 3 01:44 /dev/bus/usb/001/003 ----------libvirt xml snippet ------------ <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x8644'/> <product id='...
2014 Apr 14
2
Re: LXC + USB passthrough = Operation not permitted
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
2014 Apr 14
2
Re: LXC + USB passthrough = Operation not permitted
...t;/source> > </hostdev> > > Then I get inside the guest container and list out the usb busses we just > mounted: > > $ ll /dev/bus/usb/002/ > total 0 > drwxr-xr-x 2 root root 80 Apr 14 17:43 ./ > drwxr-xr-x 3 root root 60 Apr 14 17:43 ../ > crwx------ 1 root root 189, 129 Apr 14 17:43 002 > crwx------ 1 root root 189, 130 Apr 14 17:43 003 > > You can see the group that owns the character devices is different, and > the read/write permissions are different, too. Not sure if this is the root > of the issue, but, I noticed that...
2014 Apr 14
0
Re: LXC + USB passthrough = Operation not permitted
...t;/dev/bus/usb/002/003</char> </source> </hostdev> Then I get inside the guest container and list out the usb busses we just mounted: $ ll /dev/bus/usb/002/ total 0 drwxr-xr-x 2 root root 80 Apr 14 17:43 ./ drwxr-xr-x 3 root root 60 Apr 14 17:43 ../ crwx------ 1 root root 189, 129 Apr 14 17:43 002 crwx------ 1 root root 189, 130 Apr 14 17:43 003 You can see the group that owns the character devices is different, and the read/write permissions are different, too. Not sure if this is the root of the issue, but, I noticed that difference. In any case...
2017 Feb 07
1
Re: accessing USB as storage device through lxc container.
...>> IR800-GOS-1:~# lsusb >> Bus 001 Device 003: ID 8644:800b >> Bus 001 Device 001: ID 1d6b:0002 >> Bus 002 Device 001: ID 1d6b:0001 >> IR800-GOS-1:~# >> >> Lxc app container: >> >> root@ir800-lxc:/mnt/usb# ls -la /dev/bus/usb/001/003 >> *crwx-*----- 1 root root 189, 2 Feb 3 01:44 >> /dev/bus/usb/001/003 >> >> >> >> ----------libvirt xml snippet ------------ >> >> <hostdev mode='subsystem' type='usb' managed='yes'> >> <source> >&...
2017 Feb 03
0
Re: accessing USB as storage device through lxc container.
...would be >useful. > > >Host OS: > >IR800-GOS-1:~# lsusb >Bus 001 Device 003: ID 8644:800b >Bus 001 Device 001: ID 1d6b:0002 >Bus 002 Device 001: ID 1d6b:0001 >IR800-GOS-1:~# > >Lxc app container: > >root@ir800-lxc:/mnt/usb# ls -la /dev/bus/usb/001/003 >*crwx-*----- 1 root root 189, 2 Feb 3 01:44 >/dev/bus/usb/001/003 > > > >----------libvirt xml snippet ------------ > > <hostdev mode='subsystem' type='usb' managed='yes'> > <source> > <vendor id='0x8644...