DPDK usage discussions
 help / color / mirror / Atom feed
From: "Tan, Jianfeng" <jianfeng.tan@intel.com>
To: "Wu, Xiaoban" <Xiaoban_Wu@student.uml.edu>,
	"users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] docker container, EAL: failed to initialize virtio_user0 device
Date: Mon, 22 May 2017 11:35:49 +0800	[thread overview]
Message-ID: <3fd5da5b-3a95-7be5-ba63-ffc5b7c9bd5d@intel.com> (raw)
In-Reply-To: <BN6PR02MB2706007EB8531B08008E81FDBCFB0@BN6PR02MB2706.namprd02.prod.outlook.com>

Hi,


On 5/21/2017 11:53 AM, Wu, Xiaoban wrote:
> Hi DPDK Users,
>
>
> I am trying to use docker container and ovs(2.6.0)-dpdk(16.07) to setup a test. I want to setup two docker containers, each of them will use a virtual device (socket) created by the ovs-dpdk. The final purpose would let the two containers talk to each other.
>
>
> Setup ovs-dpdk
>
>    1.  ovsdb-tool create $ovs-dir/etc/openvswitch/conf.db $ovs-dir/share/openvswitch/vswitch.ovsschema
>    2.  ovsdb-server --remote=punix:$ovs-dir/var/run/openvswitch/db.sock --remote=db:Open_vSwitch,Open_vSwitch,manager_options --pidfile --detach
>    3.  ovs-vsctl --no-wait set Open_vSwitch . other_config:dpdk-init=true
>    4.  ovs-vsctl --no-wait set Open_vSwitch . other_config:dpdk-socket-mem="512,512"
>    5.  ovs-vswitchd  unix:$ovs-dir/var/run/openvswitch/db.sock --pidfile --detach  --log-file=$ovs-dir/temp.log
>
> Setup bridge and ports
>
>    1.  ovs-vsctl add-br br0 -- set bridge br0 datapath_type=netdev
>    2.  ovs-vsctl add-port br0 vhost-user1 -- set Interface vhost-user1 type=dpdkvhostuser ofport_request=1
>    3.  ovs-vsctl add-port br0 vhost-user2 -- set Interface vhost-user2 type=dpdkvhostuser ofport_request=2
>    4.  ovs-ofctl add-flow br0 priority=1000,in_port=1,actions=output:2
>    5.  ovs-ofctl add-flow br0 priority=1000,in_port=2,actions=output:1
>
> Run the docker container
>
>    1.  docker run -it --privileged -v $ovs-dir/var/run/openvswitch/vhost-user1:/var/run/usvhost -v /mnt/huge/:/dev/hugepages/ $docker-image bash
>
> Run the dpdk application in the docker container
>
>    1.  $dpdk-app -c 0x01 --socket-mem=128,0 --vdev=virtio_user0,path=/var/run/usvhost --file-prefix="docker1"
>
> However, I encountered this error
> PMD: vhost_user_setup(): connect error, Connection refused

Seems that OVS is not listening on this unix socket. Could you check OVS 
log to see if the vhost-user ports are created successfully?

Thanks,
Jianfeng

> PMD: virtio_user_dev_init(): backend set up fails
> PMD: virtio_user_pmd_devinit(): virtio_user_dev_init fails
> EAL: failed to initialize virtio_user0 device
>
> It seems like the application in the docker container cannot connect the socket created by the ovs-dpdk.
>
> Can anybody please help me and point out some possible solutions? Looking forward to your reply. Thanks very much for your help.
>
> Best wishes,
> Xiaoban
>

  reply	other threads:[~2017-05-22  3:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-21  3:53 Wu, Xiaoban
2017-05-22  3:35 ` Tan, Jianfeng [this message]
2017-05-23  3:44   ` Wu, Xiaoban
2017-05-23 20:21 ` Neeraj Tandon (netandon)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3fd5da5b-3a95-7be5-ba63-ffc5b7c9bd5d@intel.com \
    --to=jianfeng.tan@intel.com \
    --cc=Xiaoban_Wu@student.uml.edu \
    --cc=users@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).