> the fabrics device and writing the host NQN etc. Is there an easy way > to prove that rdma_resolve_addr is working from userland? Actually I meant "is there a way to prove that the kernel rdma_resolve_addr() works with netns?" It seems like this is the real problem. If we run commands like nvme discover & nvme connect within the netns context, the system will use the non-netns IP & RDMA stacks to connect. As an aside - this seems like it would be a major security issue for container systems, doesn't it? I'll investigate to see if the fabrics module & nvme-cli have a way to set and use the proper netns context. Thanks, Mark
