From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 8D6858DA4 for ; Thu, 31 Dec 2015 10:19:54 +0100 (CET) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga102.jf.intel.com with ESMTP; 31 Dec 2015 01:19:53 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.20,503,1444719600"; d="scan'208";a="626128552" Received: from fmsmsx105.amr.corp.intel.com ([10.18.124.203]) by FMSMGA003.fm.intel.com with ESMTP; 31 Dec 2015 01:19:53 -0800 Received: from fmsmsx152.amr.corp.intel.com (10.18.125.5) by FMSMSX105.amr.corp.intel.com (10.18.124.203) with Microsoft SMTP Server (TLS) id 14.3.248.2; Thu, 31 Dec 2015 01:19:53 -0800 Received: from shsmsx101.ccr.corp.intel.com (10.239.4.153) by FMSMSX152.amr.corp.intel.com (10.18.125.5) with Microsoft SMTP Server (TLS) id 14.3.248.2; Thu, 31 Dec 2015 01:19:52 -0800 Received: from shsmsx102.ccr.corp.intel.com ([169.254.2.133]) by SHSMSX101.ccr.corp.intel.com ([169.254.1.111]) with mapi id 14.03.0248.002; Thu, 31 Dec 2015 17:19:51 +0800 From: "Tan, Jianfeng" To: Pavel Fedin , "dev@dpdk.org" Thread-Topic: [dpdk-dev] [RFC 0/5] virtio support for container Thread-Index: AdFC5lAx4gxjgPHsRda0ClGnzG0GiAAwk/4w Date: Thu, 31 Dec 2015 09:19:50 +0000 Message-ID: References: <002a01d142e6$fbfeb4e0$f3fc1ea0$@samsung.com> In-Reply-To: <002a01d142e6$fbfeb4e0$f3fc1ea0$@samsung.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [RFC 0/5] virtio support for container X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Dec 2015 09:19:55 -0000 Hi Fedin, First of all, when you say openvswitch, are you referring to ovs-dpdk? And can you detail your test case? Like, how do you want ovs_on_host and ov= s_in_container to be connected? Through two-direct-connected physical NICs, or one vhost port in ovs_on_hos= t and one virtio port in ovs_in_container? Thanks, Jianfeng > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Pavel Fedin > Sent: Wednesday, December 30, 2015 5:47 PM > To: dev@dpdk.org > Subject: Re: [dpdk-dev] [RFC 0/5] virtio support for container >=20 > Hello everybody! >=20 > I am currently working on improved version of this patchset, and i am te= sting > it with openvswitch. I run two openvswitch instances: > on host and in container. Both ovs instances forward packets between its > LOCAL port and vhost/virtio port. This way i can > comfortably run PING between my host and container. > The problem is that the patchset seems to be broken somehow. ovs- > vswitchd fails to open dpdk0 device, and if i set --log-level=3D9 > for DPDK, i see this in the console: > --- cut --- > Broadcast message from systemd-journald@localhost.localdomain (Wed > 2015-12-30 11:13:00 MSK): >=20 > ovs-vswitchd[557]: EAL: TSC frequency is ~3400032 KHz >=20 >=20 > Broadcast message from systemd-journald@localhost.localdomain (Wed > 2015-12-30 11:13:00 MSK): >=20 > ovs-vswitchd[560]: EAL: memzone_reserve_aligned_thread_unsafe(): > memzone already exists >=20 >=20 > Broadcast message from systemd-journald@localhost.localdomain (Wed > 2015-12-30 11:13:00 MSK): >=20 > ovs-vswitchd[560]: RING: Cannot reserve memory > --- cut --- >=20 > How can i debug this? >=20 > Kind regards, > Pavel Fedin > Expert Engineer > Samsung Electronics Research center Russia >=20 >=20