From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mailout1.w1.samsung.com (mailout1.w1.samsung.com [210.118.77.11]) by dpdk.org (Postfix) with ESMTP id CEF1C5913 for ; Tue, 12 Jan 2016 08:38:30 +0100 (CET) Received: from eucpsbgm2.samsung.com (unknown [203.254.199.245]) by mailout1.w1.samsung.com (Oracle Communications Messaging Server 7.0.5.31.0 64bit (built May 5 2014)) with ESMTP id <0O0T002STX85SL30@mailout1.w1.samsung.com> for dev@dpdk.org; Tue, 12 Jan 2016 07:38:29 +0000 (GMT) X-AuditID: cbfec7f5-f79b16d000005389-7f-5694ad752d1e Received: from eusync3.samsung.com ( [203.254.199.213]) by eucpsbgm2.samsung.com (EUCPMTA) with SMTP id BC.38.21385.57DA4965; Tue, 12 Jan 2016 07:38:29 +0000 (GMT) Received: from fedinw7x64 ([106.109.131.169]) by eusync3.samsung.com (Oracle Communications Messaging Server 7.0.5.31.0 64bit (built May 5 2014)) with ESMTPA id <0O0T005VYX83GA60@eusync3.samsung.com>; Tue, 12 Jan 2016 07:38:29 +0000 (GMT) From: Pavel Fedin To: "'Tan, Jianfeng'" , dev@dpdk.org References: <1446748276-132087-1-git-send-email-jianfeng.tan@intel.com> <1452426182-86851-1-git-send-email-jianfeng.tan@intel.com> <058a01d14c7b$5cdc60d0$16952270$@samsung.com> <5693CFE4.4060405@intel.com> In-reply-to: <5693CFE4.4060405@intel.com> Date: Tue, 12 Jan 2016 10:38:26 +0300 Message-id: <009a01d14d0c$3ab6cd60$b0246820$@samsung.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-index: AQLOfZuJ4skKn5NxqR5aD7duH+7e0wGBr/PNAeo3hAkCmaBQ8ZzM8LUA Content-language: ru X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprNIsWRmVeSWpSXmKPExsVy+t/xq7qla6eEGRzv5rGY+/IHk8W7T9uZ LNpnnmWy6J79hc3i7+xWVov/v16xWhzr+cRqcejQYUaLTe8msVpcn3CB1YHL48Hlm0wevxYs ZfVoOfKW1aPxuYTH4j0vmTyaXzxn8Zh3MtDj/b6rbAEcUVw2Kak5mWWpRfp2CVwZbX8rC7bx V0z6vZC1gXEFbxcjJ4eEgInEsvkXGCFsMYkL99azgdhCAksZJb59Dehi5AKyvzNKTHjwkRkk wSagLnH66wcWEFtEwEbi5fQ9rCA2s8AZRokjO9ghGi4ySrTsvQ02iVNAU+L0zp9AzRwcwgKm Eh8XCIOEWQRUJd7s3w1WwitgKbH+5msWCFtQ4sfkeywQM7Uk1u88zgRhy0tsXvOWGeJQBYkd Z18zQtzgJvF0xkuoehGJaf/uMU9gFJqFZNQsJKNmIRk1C0nLAkaWVYyiqaXJBcVJ6blGesWJ ucWleel6yfm5mxghUfZ1B+PSY1aHGAU4GJV4eDPYp4QJsSaWFVfmHmKU4GBWEuF1CgIK8aYk VlalFuXHF5XmpBYfYpTmYFES5525632IkEB6YklqdmpqQWoRTJaJg1OqgdG7t8dELdZM8NZs r7OVC3Zf+8IXENe3I/ZGUpG1D9sSfs6Fqqvjkx/sfKKyYtsUv0kcH+TTfhd+ahW1bQ7x+7E1 oTH3yraVPZmtlsnc09uYPJOl0wzVgxPOLlvmIXhYQmXervV7p85ellp5YNa2aZ/1Sj4EuN7+ eidmXfI5nd8fb275d9Xy2EMlluKMREMt5qLiRABlevk+rgIAAA== Cc: nakajima.yoshihiro@lab.ntt.co.jp, mst@redhat.com, ann.zhuangyanying@huawei.com Subject: Re: [dpdk-dev] [PATCH 0/4] 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: Tue, 12 Jan 2016 07:38:30 -0000 Hello! > > b) With --single-file - ovs runs, but doesn't get any packets at all. When i try to ping > the container from within host side, it > > counts drops on vhost-user port. > Can you check the OVS in host side, if it prints out message of "virtio > is now ready for processing"? No, i get errors: --- cut --- Jan 12 10:27:43 nfv_test_x86_64 ovs-vswitchd[18858]: VHOST_CONFIG: new virtio connection is 38 Jan 12 10:27:43 nfv_test_x86_64 ovs-vswitchd[18858]: VHOST_CONFIG: new device, handle is 0 Jan 12 10:27:43 nfv_test_x86_64 ovs-vswitchd[18858]: VHOST_CONFIG: read message VHOST_USER_SET_OWNER Jan 12 10:27:43 nfv_test_x86_64 ovs-vswitchd[18858]: VHOST_CONFIG: read message VHOST_USER_GET_FEATURES Jan 12 10:27:43 nfv_test_x86_64 ovs-vswitchd[18858]: VHOST_CONFIG: read message VHOST_USER_SET_FEATURES Jan 12 10:27:43 nfv_test_x86_64 kernel: device ovs-netdev entered promiscuous mode Jan 12 10:27:43 nfv_test_x86_64 kernel: device ovs0 entered promiscuous mode Jan 12 10:27:43 nfv_test_x86_64 ovs-vswitchd[18858]: VHOST_CONFIG: read message VHOST_USER_SET_MEM_TABLE Jan 12 10:27:43 nfv_test_x86_64 ovs-vswitchd[18858]: VHOST_CONFIG: mapped region 0 fd:39 to:0x7f079c600000 sz:0x200000 off:0x0 align:0x200000 Jan 12 10:27:43 nfv_test_x86_64 ovs-vswitchd[18858]: VHOST_CONFIG: read message VHOST_USER_SET_VRING_CALL Jan 12 10:27:43 nfv_test_x86_64 ovs-vswitchd[18858]: VHOST_CONFIG: vring call idx:0 file:49 Jan 12 10:27:43 nfv_test_x86_64 ovs-vswitchd[18858]: VHOST_CONFIG: read message VHOST_USER_SET_VRING_NUM Jan 12 10:27:43 nfv_test_x86_64 ovs-vswitchd[18858]: VHOST_CONFIG: read message VHOST_USER_SET_VRING_BASE Jan 12 10:27:43 nfv_test_x86_64 ovs-vswitchd[18858]: VHOST_CONFIG: read message VHOST_USER_SET_VRING_ADDR Jan 12 10:27:43 nfv_test_x86_64 ovs-vswitchd[18858]: VHOST_CONFIG: (0) Failed to find desc ring address. --- cut --- Kind regards, Pavel Fedin Expert Engineer Samsung Electronics Research center Russia