On Tue, 2018-12-04 at 08:48 -0800, Stephen Hemminger wrote: > On Fri, 30 Nov 2018 14:06:52 -0500 (EST) > Mohammed Gamal <mmo...@redhat.com> wrote: > > > ----- Stephen Hemminger <step...@networkplumber.org> wrote: > > > On Fri, 30 Nov 2018 12:04:41 +0100 > > > Mohammed Gamal <mga...@redhat.com> wrote: > > > > > > > Hi All, > > > > I am having the following errors when I run testpmd with the > > > > netvsc > > > > driver and --txq 2 and --rxq 2 options: > > > > > > > > testpmd: create a new mbuf pool <mbuf_pool_socket_0>: n=155456, > > > > size=2176, socket=0 > > > > testpmd: preferred mempool ops selected: ring_mp_mc > > > > Configuring Port 0 (socket 0) > > > > hn_dev_configure(): >> > > > > hn_rndis_link_status(): link status 0x40020006 > > > > hn_subchan_configure(): open 1 subchannels > > > > vmbus_uio_get_subchan(): invalid subchannel id 0 > > > > hn_subchan_configure(): open subchannel failed: -5 > > > > hn_dev_configure(): subchannel configuration failed > > > > Port0 dev_configure = -5 > > > > hn_dev_rx_queue_release(): >> > > > > hn_dev_rx_queue_release(): >> > > > > hn_dev_tx_queue_release(): >> > > > > hn_dev_tx_queue_release(): >> > > > > Fail to configure port 0 > > > > EAL: Error - exiting with code: 1 > > > > Cause: Start ports failed > > > > > > > > Multiq support was enabled and kernel module was loaded. The > > > > full > > > > command line was: > > > > ./testpmd -l 0-1 -n 2 --log-level=8 --log-level='pmd.*,8' -- > > > > log- > > > > level='bus.vmbus,8' -- --port-topology=chained --forward- > > > > mode=rxonly -- > > > > stats-period 1 --eth-peer=0,00:15:5d:1e:20:c0 --txq 2 --rxq 2 > > > > > > > > I am running latest upstream kernel from the Linus tree and > > > > latest DPDK > > > > upstream from git.dpdk.org. > > > > > > > > Could you also reproduce this? If not, what could I be > > > > misssing? > > > > > > > > Regards, > > > > Mohammed > > > > > > Investigating now. > > > Does single queue work for you? > > > > Yes it does. > > What version of Windows are you running on? Multi-queue requires > WS2016 or later. > The driver is missing a check of NDIS version, will add that.
I am running WS2016
