On Fri, Oct 4, 2019 at 3:33 AM Benoit Ganne (bganne) <bga...@cisco.com> wrote:
> Hi, > > Yes containers usually do not update /dev after creation, so any device > that shows up dynamically afterwards won't be available by default. Note > this is not specific to VPP. OK cool, that is what it was looking like... To access PCI devices from userspaces you'll need access to either > /dev/vfio/* or /dev/uio* device nodes depending of the driver. > Yeah, DPDK is looking for /dev/uio*... > You have several options: > 1) make sure the device showed up before starting the container so that > they will be populated > I have tried this, and it doesn't work. > 2) create you container using '-v /dev:/dev' to bind mount /dev: every > changes in host /dev is visible to container > Also, does not work. > 3) use mknod to make the device nodes in the container > This, I expected to work, but it does not. > 4) run udev in your container > Could you clarify a bit what you mean by this? Or how to set that up? udev is, of course, already running on the host system. In each of the cases above where I said "still doesn't work", when the /dev/uio* is present, it is found. However, it then leads to this error as reported by vppctl's "show log" command: 2019/10/04 21:23:48:566 notice dpdk EAL: PCI device 0000:06:00.1 on NUMA socket -1 2019/10/04 21:23:48:566 notice dpdk EAL: Invalid NUMA socket, default to 0 2019/10/04 21:23:48:566 notice dpdk EAL: probe driver: 8086:15e4 net_ixgbe I've not yet chased that down. Any chance there is more direct knowledge about it? I suspect the real problem is that there is some form of namespace problem that is preventing the device from being used (seen?) properly. Does the /dev entry belong to a specific namespace? And if VPP/DPDK doesn't actually make the device (via the driver call), does it end up in the wrong namespace still? Best > ben > Thanks, jdl
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#14134): https://lists.fd.io/g/vpp-dev/message/14134 Mute This Topic: https://lists.fd.io/mt/34386250/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
