similar to: If it's possible for a third-party PCIe card to be shared by multiple containers

Dear Daniel, The thirty-party PCIe card is based on the Xilinx’ FPGA which is off the shelf, the main features are as follows: 1) x8 Gen3, 8Gb/s per lane/direction 2) MSI and legacy interrupt support 3) Scatter-gather packet DMA engine provide by Northwest Logic We hope multiple Linux Containers to access the PCIe card in time division mode, for example, during slot 1, lxc1 read/write the PCIe

Dear Daniel, I found that lxc driver doesn't support hostdev with type of 'pci'. As you mentioned before, I tried to expose the device node (the PCIe card) to the container, my XML is as follow: <devices> <hostdev mode='subsystem' type='pci' managed='yes'> <source> <address bus='0x01' slot='0x00'

On Thu, Jan 16, 2014 at 08:55:53AM +0000, WANG Cheng D wrote: > Dear Daniel, > > The thirty-party PCIe card is based on the Xilinx’ FPGA which is off the shelf, the main features are as follows: > 1) x8 Gen3, 8Gb/s per lane/direction > 2) MSI and legacy interrupt support > 3) Scatter-gather packet DMA engine provide by Northwest Logic > We hope multiple Linux Containers to

On Wed, Jan 15, 2014 at 12:58:54AM +0000, WANG Cheng D wrote: > Dear all, > > I have a thirty-party PCIe card in my host which can work properly in native mode. > > I wonder if this card can be shared by multiple containers. > > As far as the network interface is concerned, too many efforts have > been made for it. Two dedicated cgroup resource schedulers/subsystem >

Hi all Each lxc container on node have mounted tmpfs for cgroups tree: [root-inside-lxc@tst1 ~]# mount | grep cgroups cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct,cpu) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) cgroup on

Hello Hendrik Can you help input 2 commands 'mount' and 'df -TPh' on OMV, and post the output to us, thank you. -- Regards, Jones Syue | ??? QNAP Systems, Inc.

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

I''m trying to use this feature of qgroup: btrfs qgroup assign <srcid> <destid> <path> Assigns the lower level qgroup src to the higher level qgroup dest in the btrfs found in <path>. It is used to build qgroup hierarchies. However, I fail to understand how this feature should work, and I''m getting "ERROR: bad relation requested":

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 10/17/2018 08:56 AM, Andrea Bolognani wrote: > On Wed, 2018-10-17 at 10:50 +0800, Han Han wrote: >> In libvirt, I found pcie-expander-bus controller doesn't support pcie-to-pci-bridge and pcie-switch-upstream-port. > [...] >> # virsh -k0 -K0 define /tmp/c.xml > Aside: the -k and -K virsh options are documented as > > -k | --keepalive-interval=NUM >

In libvirt, I found pcie-expander-bus controller doesn't support pcie-to-pci-bridge and pcie-switch-upstream-port. Version: libvirt-4.9 # cat /tmp/c.xml ... <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='pcie-expander-bus'> <model name='pxb-pcie'/>

hi all, I am using lxc with libvirt. But I can't boot lxc container by libvirt 1.0.3(libvirt 0.9.8 works) . Below is my environment. Do I miss something? lxc1.xml:<domain type='lxc'> <name>lxc1</name> <memory>1024000</memory> <cputune> <shares>100</shares> </cputune> <os> <type>exe</type>

Error on domain option !! Sep 25 12:04:33 ubuntucliente lightdm[702]: (mount.c:664): Password will be sent to helper as-is. Sep 25 12:04:33 ubuntucliente lightdm[702]: command: 'mount' '-t' 'cifs' '//domain-server2/FS_PRUEBA_3' '/home/prueba3/compartido' '-o' 'username=prueba3,uid=50006,gid=50027,username=prueba3,uid=50006,gid=50027,domain'

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

Greetings all- I need to purchase a PCIe SATA or SAS controller(non-raid) for a Supermicro 2U system. It should be directly bootable. Any recommendations? The system will be running CentOS 5.4 as an LTSP system. Thanks! --Tim

Hi Folks: I am oot able to add HP Intel 4Port PCIe to a linux hvm domain. HW is a HP DC7900. ErrorMessage: VmError: pci: to avoid potential security issue, 0000:22:00.0 is not allowed to be assigned to guest since it is behind PCIe switch that does not support or enable ACS. I also added in /etc/xen/xend-config.sxp: pci-passthrough-strict-check no pci-dev-assign-strict-check no but no

Signed-off-by: Karol Herbst <kherbst at redhat.com> Reviewed-by: Lyude Paul <lyude at redhat.com> --- drm/nouveau/nvkm/subdev/pci/gk104.c | 8 ++++---- drm/nouveau/nvkm/subdev/pci/gp100.c | 10 ++++++++++ drm/nouveau/nvkm/subdev/pci/priv.h | 5 +++++ 3 files changed, 19 insertions(+), 4 deletions(-) diff --git a/drm/nouveau/nvkm/subdev/pci/gk104.c

So, in the ongoing saga of the unusual 1U short-depth workstation, we have narrowed the field to two choices. Both entrants are configured with 16GB memory (4x4GB), two 2.5" drives (1x250GB SSD and 1x1TB HDD), and an NVIDIA NVS510 graphic card (quad display): 1) SuperMicro 5017R-MF, Xeon E5-2609 processor 2) SuperMicro 5017C-LF, Xeon E3-1220 processor (I wish SuperMicro had a list of their

everything was taken from nvgpu. Main reason for adding is to improve stability of the PCIe link changing code as we might want to depend on it for a workaround fixing our infamous runpm issues on recent laptops Karol Herbst (3): pci: force disable ASPM before changing the link speed pci/gk104: enable dl_mgr safe mode pci/gk104: wait for ltssm idle before changing the link

one rename and one enable patch. Tested on hardware and confirmed with traces Karol Herbst (2): pci: Rename g94 to g92 pci/g92: Enable changing pcie link speeds drm/nouveau/include/nvkm/subdev/pci.h | 2 +- drm/nouveau/nvkm/engine/device/base.c | 22 +++++++++++----------- drm/nouveau/nvkm/subdev/pci/Kbuild | 2 +- drm/nouveau/nvkm/subdev/pci/{g94.c => g92.c} |