[SPDK] NVMeF Taget Setup

[yzhu <yzhu at cs.fsu.edu>]

[-- Attachment #1: Type: text/plain, Size: 2056 bytes --]

Hi all,

I got an error when trying to set up the NVMeF Target. The error says 
"could not found NVMe controller at PCI address xxxxx". However, I do 
have a NVMe drive with our system. I was wondering if someone has an 
idea about this. I attached my configuration and error I got below.

1. Configuration
# Direct controller
[Subsystem1]
   NQN nqn.2016-06.io.spdk:cnode1
   Core 0
   Mode Direct
   Listen RDMA 10.10.16.10:4420
   Host nqn.2016-06.io.spdk:init
   NVMe 0000:04:00.0


2. Error
Starting Intel(R) DPDK initialization ...
[ DPDK EAL parameters: nvmf -c 1 --file-prefix=spdk12027 
--base-virtaddr=0x1000000000 --proc-type=auto ]
EAL: Detected 40 lcore(s)
EAL: Auto-detected process type: PRIMARY
EAL: No free hugepages reported in hugepages-1048576kB
EAL: Probing VFIO support...
EAL: PCI device 0000:04:00.0 on NUMA socket 0
EAL:   probe driver: 8086:953 spdk_nvme
Occupied cpu core mask is 0x1
Occupied cpu socket mask is 0x1
EAL: PCI device 0000:04:00.0 on NUMA socket 0
EAL:   probe driver: 8086:953 spdk_nvme
Ioat Copy Engine Offload Enabled
EAL: PCI device 0000:04:00.0 on NUMA socket 0
EAL:   probe driver: 8086:953 spdk_nvme
Probing device 0000:04:00.0
Total cores available: 1
Reactor started on core 0 on socket 0
*** RDMA Transport Init ***
allocated subsystem nqn.2014-08.org.nvmexpress.discovery on lcore 0 on 
socket 0
allocated subsystem nqn.2016-06.io.spdk:cnode1 on lcore 0 on socket 0
Subsystem nqn.2016-06.io.spdk:cnode1 is configured to run on a CPU core 
0 belonging to a different NUMA node than the associated NIC. This may 
result in reduced performance.
The NIC is on socket 1
The Subsystem is on socket 0
conf.c: 565:spdk_nvmf_construct_subsystem: ***ERROR*** Could not find 
NVMe controller at PCI address 0000:04:00.0
nvmf_tgt.c: 336:spdk_nvmf_startup: ***ERROR*** spdk_nvmf_parse_conf() 
failed
EAL: PCI device 0000:04:00.0 on NUMA socket 0
EAL:   probe driver: 8086:953 spdk_nvme
EAL: Requested device 0000:04:00.0 cannot be used

Thanks in advance,
Yue