[ovs-dev] Fwd: [Dpdk-ovs] dpdk ovs

Thu Oct 1 01:03:11 UTC 2015

Hi All,

I tried to install DPDK-OVS (2.0) on a virtual machine (initiated using
virt-manger). But dpdk interface creation fails with the following below
error
====== ovs command fails
stack at stack-Standard-PC-i440FX-PIIX-1996:~/work/ovs/ovs-2.4.0/vswitchd$
sudo ovs-vsctl add-port ovs dpdk0 -- set Interface dpdk0 type=dpdk
ovs-vsctl: Error detected while setting up 'dpdk0'.  See ovs-vswitchd log
for details.

DEBUG LOGS:
During vswitchd initialization, PCI device mapping seem to indicate socket
-1, is this fine?? It should indicate the mapped memory like this, right?
"EAL:   PCI memory mapped at 0x7f8380024000"

======= ovs-vswitchd initialization logs
EAL: Requesting 512 pages of size 2MB from socket 0
EAL: TSC frequency is ~2300002 KHz
EAL: WARNING: cpu flags constant_tsc=no nonstop_tsc=no -> using unreliable
clock cycles !
EAL: Master lcore 0 is ready (tid=97048b40;cpuset=[0])
PMD: ENICPMD trace: rte_enic_pmd_init
EAL: PCI device 0000:00:03.0 on NUMA socket -1
EAL:   probe driver: 1af4:1000 rte_virtio_pmd
EAL: PCI device 0000:00:07.0 on NUMA socket -1
EAL:   probe driver: 1af4:1000 rte_virtio_pmd
Zone 0: name:<MALLOC_S0_HEAP_0>, phys:0x1d000000, len:0xb00000,
virt:0x7f6f7cc00000, socket_id:0, flags:0
Zone 1: name:<RG_MP_log_history>, phys:0x1c800000, len:0x2080,
virt:0x7f6f95600000, socket_id:0, flags:0
Zone 2: name:<MP_log_history>, phys:0x1db00000, len:0x28a0c0,
virt:0x7f6f7d700000, socket_id:0, flags:0
Zone 3: name:<rte_eth_dev_data>, phys:0x1c802080, len:0x1f400,
virt:0x7f6f95602080, socket_id:0, flags:0
Zone 4: name:<port0_cvq>, phys:0x1c822000, len:0x2000, virt:0x7f6f95622000,
socket_id:0, flags:0
Zone 5: name:<port0_cvq_hdrzone>, phys:0x1c824000, len:0x1000,
virt:0x7f6f95624000, socket_id:0, flags:0

=====
 cat /proc/meminfo | grep -i huge
AnonHugePages:    212992 kB
HugePages_Total:    2048
HugePages_Free:     1536
HugePages_Rsvd:        0
HugePages_Surp:        0
Hugepagesize:       2048 kB

Please let me know if I am missing something.

Thanks
Gayathri

On Fri, Sep 4, 2015 at 10:06 AM, Flavio Leitner <fbl at sysclose.org> wrote:

> On Thu, Sep 03, 2015 at 12:16:57PM -0700, Gayathri wrote:
> > Hi all,
> >
> > Plz comment.
> >
> > Regards,
> > gayathri
> >
> > ---------- Forwarded message ----------
> > From: Gray, Mark D <mark.d.gray at intel.com>
> > Date: Thu, Sep 3, 2015 at 12:54 AM
> > Subject: RE: [Dpdk-ovs] dpdk ovs
> > To: Gayathri <gd0204 at gmail.com>, "dpdk-ovs at lists.01.org" <
> > dpdk-ovs at lists.01.org>
> >
> >
> > I think this refers to OVS so you should post to ovs-dev.
> >
> > > -----Original Message-----
> > > From: Dpdk-ovs [mailto:dpdk-ovs-bounces at lists.01.org] On Behalf Of
> > > Gayathri
> > > Sent: Wednesday, September 2, 2015 11:06 PM
> > > To: dpdk-ovs at lists.01.org
> > > Subject: [Dpdk-ovs] dpdk ovs
> > >
> > > Hi *,
> > >
> > > We were looking into having VNFs working on DPDK ovs within a VM. These
> > > VMs with the VNF will be running in turn on a host that is running
> already
> > > DPDK ovs. All documents that I have seen so far only indicate DPDK
> within
> > > the quest (with DPDK ovs on the HOST) and not DPDK with ovs in the
> guest &
> > > host. Please let me know if this is even possible.
>
> DPDK enabled OVS runs in userspace, so it doesn't matter whether is
> virtualized environment or not.
>
> What you need is DPDK support for the interfaces.  If you are on the
> host side, then DPDK needs to support the physical NIC.  If it's in
> the virtualized environment, then DPDK needs to support the virtual
> NIC provided.
>
> There is the virtio-pmd in DPDK2.0 for KVM/virtio environments.
>
> fbl
>
>