From: Sergey Matov <smatov@mirantis.com>
To: shyam yeduru <yedurushyam@hotmail.com>
Cc: "users@dpdk.org" <users@dpdk.org>,
"sy00454302@techmahindra.com" <sy00454302@techmahindra.com>,
yeduru shyam <yedurushyam@gmail.com>
Subject: Re: [dpdk-users] OVS Switch with DPDK
Date: Wed, 22 Jun 2016 09:37:40 +0300 [thread overview]
Message-ID: <CAPykWKECA+SQtYZqa6nCoqauN661+WdPX5LEvBu-A60PVi5RNQ@mail.gmail.com> (raw)
In-Reply-To: <BLU170-W44D2A3897229A599E44E32AB2C0@phx.gbl>
Hello.
Have you done dpdk-binding before adding DPDK interface to your bridge? It
can be done via (your DPDK dir)/tools/dpdk_nic_bind.py script.
2016-06-22 9:23 GMT+03:00 shyam yeduru <yedurushyam@hotmail.com>:
> Hi Team,
>
> We have a setup at our lab to demonstrate DPDK with OVS and With-Out. Here
> are my configuration details and error message.
>
> Hardware : HP DL 380 G8
> OS - Ubuntu 16.0.4
> OVS Package - 2.5
> DPDK has been installed along with OVS
>
> Packages installed : apt-get install openvswitch-switch-dpdk uvtool
> qemu-kvm
>
> Procedure is as follows:
> 1.0 enabled iommu on Kernel
> 2.0 enalbled hugepages
> NR_2M_PAGES=4096">> /etc/dpdk/dpdk.conf
> root@ovskvm1:~# mount | column -t | grep huge
> cgroup on /sys/fs/cgroup/hugetlb
> type cgroup
> (rw,nosuid,nodev,noexec,relatime,hugetlb,release_agent=/run/cgmanager/agents/cgm-release-agent.hugetlb,nsroot=/)
> hugetlbfs on /dev/hugepages
> type hugetlbfs (rw,relatime)
> hugetlbfs-kvm on /run/hugepages/kvm
> type hugetlbfs (rw,relatime,mode=775,gid=111)
> nodev on /var/opt/huge
> type hugetlbfs (rw,relatime,pagesize=1GB)
> hugetlb on /run/lxcfs/controllers/hugetlb
> type cgroup
> (rw,relatime,hugetlb,release_agent=/run/cgmanager/agents/cgm-release-agent
> hugetlb,nsroot=/)
>
> 3.0 OVS conf settings
>
> DPDK_OPTS='--dpdk -c 0x1 -n 4 -m 2048 --vhost-owner libvirt-qemu:kvm
> --vhost-perm 0664'
>
>
> 4.0 Connecting dpdk0 interface and two guests. We got issue while adding
> dpdko interface
>
> root@ovskvm1:~# ovs-vsctl show
> 0ee7d41d-3f51-43ae-9181-bb23aa81ebc7
> Bridge "ovsdpdkbr0"
> Port "vhost-user-2"
> Interface "vhost-user-2"
> type: dpdkvhostuser
> Port "vhost-user-1"
> Interface "vhost-user-1"
> type: dpdkvhostuser
> Port "ovsdpdkbr0"
> Interface "ovsdpdkbr0"
> type: internal
> Port "dpdk0"
> Interface "dpdk0"
> type: dpdk
> error: "could not open network device dpdk0 (No such
> device)"
> ovs_version: "2.5.0"
> root@ovskvm1:~#
>
> ovs log
>
> root@ovskvm1:~# tailf /var/log/openvswitch/ovs-vswitchd.log
> 2016-06-22T06:10:46.041Z|00015|bridge|INFO|bridge ovsdpdkbr0: added
> interface ovsdpdkbr0 on port 65534
> 2016-06-22T06:10:46.041Z|00016|bridge|INFO|bridge ovsdpdkbr0: using
> datapath ID 00001e82be6ada4d
> 2016-06-22T06:10:46.041Z|00017|connmgr|INFO|ovsdpdkbr0: added service
> controller "punix:/var/run/openvswitch/ovsdpdkbr0.mgmt"
> 2016-06-22T06:10:46.079Z|00018|bridge|INFO|ovs-vswitchd (Open vSwitch)
> 2.5.0
> 2016-06-22T06:10:53.089Z|00019|memory|INFO|183016 kB peak resident set
> size after 10.2 seconds
> 2016-06-22T06:10:53.089Z|00020|memory|INFO|handlers:11 ports:1
> revalidators:5 rules:5
> 2016-06-22T06:18:16.397Z|00021|bridge|INFO|bridge ovsdpdkbr1: added
> interface ovsdpdkbr1 on port 65534
> 2016-06-22T06:18:16.397Z|00022|bridge|INFO|bridge ovsdpdkbr1: using
> datapath ID 00002e9f58d5d440
> 2016-06-22T06:18:16.397Z|00023|connmgr|INFO|ovsdpdkbr1: added service
> controller "punix:/var/run/openvswitch/ovsdpdkbr1.mgmt"
> 2016-06-22T06:18:28.972Z|00024|bridge|WARN|could not open network device
> dpdk0 (No such device)
>
> OVS-DPDK Process:
>
> root@ovskvm1:~# ps -ef|grep ovs|grep dpdk
> root 3568 1 0 12:31 ? 00:00:00 ovs-vswit... --dpdk -c 0x1
> -n 4 -m 2048 --vhost-owner libvirt-qemu:kvm --vhost-perm 0664 --
> unix:/var/run/openvswitch/db.sock -vconsole:emer -vsyslog:err -vfile:info
> --mlockall --no-chdir --log-file=/var/log/openvswitch/ovs-vswitchd.log
> --pidfile=/var/run/openvswitch/ovs-vswitchd.pid --detach --monitor
> root 3569 3568 99 12:31 ? 00:00:07 ovs-vswitchd --dpdk -c 0x1
> -n 4 -m 2048 --vhost-owner libvirt-qemu:kvm --vhost-perm 0664 --
> unix:/var/run/openvswitch/db.sock -vconsole:emer -vsyslog:err -vfile:info
> --mlockall --no-chdir --log-file=/var/log/openvswitch/ovs-vswitchd.log
> --pidfile=/var/run/openvswitch/ovs-vswitchd.pid --detach --monitor
>
> Can some one guide us , Where are we failing and how to over come this
> issue.
>
> Thanks
> Shyam Yeduru
>
>
>
>
--
*Best Regards*
*Sergey Matov*
*Mirantis Inc*
next prev parent reply other threads:[~2016-06-22 6:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 6:23 shyam yeduru
2016-06-22 6:37 ` Sergey Matov [this message]
[not found] ` <BLU170-W123F6B04531DE26D9640B3FAB2C0@phx.gbl>
[not found] ` <CAPykWKEa4DT42ftXdsOmp94G2zcewEUbdTKYo8PgJUbLPKmFgA@mail.gmail.com>
2016-06-22 8:57 ` shyam yeduru
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=CAPykWKECA+SQtYZqa6nCoqauN661+WdPX5LEvBu-A60PVi5RNQ@mail.gmail.com \
--to=smatov@mirantis.com \
--cc=sy00454302@techmahindra.com \
--cc=users@dpdk.org \
--cc=yedurushyam@gmail.com \
--cc=yedurushyam@hotmail.com \
/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).