From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from NAM02-SN1-obe.outbound.protection.outlook.com (mail-sn1nam02on0058.outbound.protection.outlook.com [104.47.36.58]) by dpdk.org (Postfix) with ESMTP id E62F223B for ; Sun, 21 May 2017 05:53:50 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=studentuml.onmicrosoft.com; s=selector1-student-uml-edu; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=bHqiGeYAkkkAchwgLbA35Aad/axQ4arzhKAf4sIlLO0=; b=LrHZRiADNKkcEiERnc+pyU6Jlsn0cEc9Y/gDCSYfKtIHOG16y8ZVZFE3S04ZGzZYq+o7P/Ughsw8+Uzsqp2S2UB9pZYODR8ItH3r6BT/Ngry4ovB4cJ9UjAconzh5eLqn949Eqg3Rt22e2x+1NlH68SAdO3ubADNTnQtpw+6Obo= Received: from BN6PR02MB2706.namprd02.prod.outlook.com (10.175.95.20) by BN6PR02MB2707.namprd02.prod.outlook.com (10.175.95.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1101.14; Sun, 21 May 2017 03:53:48 +0000 Received: from BN6PR02MB2706.namprd02.prod.outlook.com ([10.175.95.20]) by BN6PR02MB2706.namprd02.prod.outlook.com ([10.175.95.20]) with mapi id 15.01.1101.019; Sun, 21 May 2017 03:53:48 +0000 From: "Wu, Xiaoban" To: "users@dpdk.org" Thread-Topic: docker container, EAL: failed to initialize virtio_user0 device Thread-Index: AQHS0eW1+CBYoW4Uc0S8vnojCg47Ow== Date: Sun, 21 May 2017 03:53:48 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: dpdk.org; dkim=none (message not signed) header.d=none;dpdk.org; dmarc=none action=none header.from=student.uml.edu; x-originating-ip: [2603:10b6:404:f5:cafe::b4] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; BN6PR02MB2707; 7:KQosOEKHGsOIG/fjoSFWWuzfjR+GigEoBckdMa5+gyWQPJduTgNWS3xkS6v+H3lUiu6FQfkWwf5aHUjofvlvDgOsFnml/a2c+k4iNofSaJrbjMHJI5Cu5gwyZw5qweFw9W3jEfrHV3anBk73jUQsMGeoxvT78TNjeA8jZtZ7LVb8Anm3Tm5+tuS59f7Y7muSH05MN/4KgM8JPTw1GuRFA9OiyUR0We0bT8hPmuPZtSoHBiP2o4aU10XDViI7fyj0MlZBvzMfHnnDmzNbOz6Mqk2JvFqIm2saosbf5mQnQbZ9IyiVVATzPIaLxjbJdkBn5VNoMHULR3MXIfJw2+j4aQ== x-ms-traffictypediagnostic: BN6PR02MB2707: x-ms-office365-filtering-correlation-id: 3bdb4c09-1ebc-4c1e-c7c8-08d49ffcfcad x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(201703131423075)(201703031133081); SRVR:BN6PR02MB2707; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(21532816269658); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040450)(601004)(2401047)(8121501046)(5005006)(3002001)(93006095)(93001095)(10201501046)(6041248)(20161123560025)(20161123558100)(20161123564025)(20161123562025)(201703131423075)(201702281529075)(201702281528075)(201703061421075)(201703061406153)(20161123555025)(6072148); SRVR:BN6PR02MB2707; BCL:0; PCL:0; RULEID:; SRVR:BN6PR02MB2707; x-forefront-prvs: 03142412E2 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(39410400002)(39450400003)(39840400002)(39400400002)(53474002)(45914002)(53936002)(50986999)(6116002)(6506006)(72206003)(86362001)(2501003)(3280700002)(2900100001)(81166006)(8676002)(3660700001)(5660300001)(8936002)(7696004)(33656002)(19627405001)(102836003)(54356999)(75432002)(2906002)(6606003)(74316002)(88552002)(55016002)(54896002)(6436002)(478600001)(9686003)(122556002)(42882006)(25786009)(110136004)(2351001)(6916009)(38730400002)(53336002)(99286003)(5640700003)(77096006)(189998001); DIR:OUT; SFP:1101; SCL:1; SRVR:BN6PR02MB2707; H:BN6PR02MB2706.namprd02.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM MIME-Version: 1.0 X-OriginatorOrg: student.uml.edu X-MS-Exchange-CrossTenant-originalarrivaltime: 21 May 2017 03:53:48.2572 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 4c25b8a6-17f7-46f9-83f0-54734ab81fb1 X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR02MB2707 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-users] docker container, EAL: failed to initialize virtio_user0 device X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 May 2017 03:53:51 -0000 Hi DPDK Users, I am trying to use docker container and ovs(2.6.0)-dpdk(16.07) to setup a t= est. 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 t= wo containers talk to each other. Setup ovs-dpdk 1. ovsdb-tool create $ovs-dir/etc/openvswitch/conf.db $ovs-dir/share/ope= nvswitch/vswitch.ovsschema 2. ovsdb-server --remote=3Dpunix:$ovs-dir/var/run/openvswitch/db.sock --= remote=3Ddb:Open_vSwitch,Open_vSwitch,manager_options --pidfile --detach 3. ovs-vsctl --no-wait set Open_vSwitch . other_config:dpdk-init=3Dtrue 4. ovs-vsctl --no-wait set Open_vSwitch . other_config:dpdk-socket-mem= =3D"512,512" 5. ovs-vswitchd unix:$ovs-dir/var/run/openvswitch/db.sock --pidfile --d= etach --log-file=3D$ovs-dir/temp.log Setup bridge and ports 1. ovs-vsctl add-br br0 -- set bridge br0 datapath_type=3Dnetdev 2. ovs-vsctl add-port br0 vhost-user1 -- set Interface vhost-user1 type= =3Ddpdkvhostuser ofport_request=3D1 3. ovs-vsctl add-port br0 vhost-user2 -- set Interface vhost-user2 type= =3Ddpdkvhostuser ofport_request=3D2 4. ovs-ofctl add-flow br0 priority=3D1000,in_port=3D1,actions=3Doutput:2 5. ovs-ofctl add-flow br0 priority=3D1000,in_port=3D2,actions=3Doutput:1 Run the docker container 1. docker run -it --privileged -v $ovs-dir/var/run/openvswitch/vhost-use= r1:/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=3D128,0 --vdev=3Dvirtio_user0,path=3D/= var/run/usvhost --file-prefix=3D"docker1" However, I encountered this error PMD: vhost_user_setup(): connect error, Connection refused 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 so= cket created by the ovs-dpdk. Can anybody please help me and point out some possible solutions? Looking f= orward to your reply. Thanks very much for your help. Best wishes, Xiaoban