From: 王志克 <wangzhike@jd.com>
To: "Tan, Jianfeng" <jianfeng.tan@intel.com>,
"avi.cohen@huawei.com" <avi.cohen@huawei.com>,
"users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] VIRTIO for containers
Date: Tue, 24 Oct 2017 03:15:31 +0000 [thread overview]
Message-ID: <6DAF063A35010343823807B082E5681F41D2BDBD@mbx05.360buyAD.local> (raw)
In-Reply-To: <0d678703-5fbc-c999-0009-4b4b1dfcb20a@intel.com>
Thanks Jianfeng.
I finally realized that I used DPDK16.11 which does NOT support this function.
Then I use latest DPDK (17.05.2) and OVS (2.8.1), but still does not work.
ovs-vsctl add-port br0 virtiouser0 -- set Interface virtiouser0 type=dpdk options:dpdk-devargs=virtio_user0,path=/dev/vhost-net
ovs-vsctl: Error detected while setting up 'virtiouser0': could not add network device virtiouser0 to ofproto (No such device). See ovs-vswitchd log for details.
ovs-vsctl: The default log directory is "/var/log/openvswitch".
lsmod |grep vhost
vhost_net 18152 0
vhost 33338 1 vhost_net
macvtap 22363 1 vhost_net
tun 27141 6 vhost_net
2017-10-23T19:00:42.743Z|00163|netdev_dpdk|INFO|Device 'virtio_user0,path=/dev/vhost-net' attached to DPDK
2017-10-23T19:00:42.743Z|00164|netdev_dpdk|WARN|Rx checksum offload is not supported on port 2
2017-10-23T19:00:42.743Z|00165|netdev_dpdk|ERR|Interface virtiouser0 MTU (1500) setup error: Invalid argument
2017-10-23T19:00:42.743Z|00166|netdev_dpdk|ERR|Interface virtiouser0(rxq:1 txq:1) configure error: Invalid argument
2017-10-23T19:00:42.743Z|00167|dpif_netdev|ERR|Failed to set interface virtiouser0 new configuration
2017-10-23T19:00:42.743Z|00168|bridge|WARN|could not add network device virtiouser0 to ofproto (No such device)
Which versions (dpdk and ovs) are you using? Thanks
Br,
Wang Zhike
From: Tan, Jianfeng [mailto:jianfeng.tan@intel.com]
Sent: Saturday, October 21, 2017 12:55 AM
To: 王志克; avi.cohen@huawei.com; dpdk-ovs@lists.01.org; users@dpdk.org
Subject: Re: VIRTIO for containers
Hi Zhike,
On 10/20/2017 5:24 PM, 王志克 wrote:
I read this thread, and try to do the same way (legacy containers connect to ovs+dpdk). However, I meet following error when creating ovs port.
ovs-vsctl add-port br0 virtiouser0 -- set Interface virtiouser0 type=dpdk options:dpdk-devargs=net_virtio_user0,path=/dev/vhost-net
ovs-vsctl: Error detected while setting up 'virtiouser0': Error attaching device 'net_virtio_user0,path=/dev/vhost-net' to DPDK. See ovs-vswitchd log for details.
ovs-vsctl: The default log directory is "/var/log/openvswitch".
It should not try to connect this file /dev/vhost-net if this file exists, instead it will use ioctls on it. So please check if you have vhost and vhost-net ko probed into kernel.
Thanks,
Jianfeng
Debug shows that it calls virtio_user_dev_init()->vhost_user_setup(), and failed in connect() with target /dev/vhost-net. The errno is ECONNREFUSED.
Below command indeed shows no one is listening.
lsof | grep vhost-net
In kernel OVS, I guess qemu-kvm would listne to /dev/vhost-net. But for ovs_dpdk and container, what extra work need be done? Appreciate any help.
Br,
Wang Zhike
next prev parent reply other threads:[~2017-10-24 3:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 9:24 王志克
2017-10-20 16:54 ` Tan, Jianfeng
2017-10-24 3:15 ` 王志克 [this message]
2017-10-24 9:45 ` 王志克
2017-10-25 7:34 ` Tan, Jianfeng
2017-10-25 9:58 ` 王志克
2017-10-26 8:53 ` Tan, Jianfeng
2017-10-26 12:53 ` 王志克
2017-10-27 1:58 ` Tan, Jianfeng
2017-10-31 4:25 ` 王志克
2017-11-01 2:58 ` Tan, Jianfeng
-- strict thread matches above, loose matches on Subject: below --
2017-06-25 15:13 Avi Cohen (A)
2017-06-26 3:14 ` Tan, Jianfeng
2017-06-26 6:16 ` Avi Cohen (A)
2017-06-26 11:58 ` Tan, Jianfeng
2017-06-26 12:06 ` Avi Cohen (A)
2017-06-27 14:22 ` Tan, Jianfeng
2017-06-28 6:45 ` Avi Cohen (A)
2017-07-03 7:21 ` Tan, Jianfeng
2017-07-09 15:32 ` Avi Cohen (A)
2017-07-10 3:28 ` Tan, Jianfeng
2017-07-10 6:49 ` Avi Cohen (A)
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=6DAF063A35010343823807B082E5681F41D2BDBD@mbx05.360buyAD.local \
--to=wangzhike@jd.com \
--cc=avi.cohen@huawei.com \
--cc=jianfeng.tan@intel.com \
--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).