[dpdk-dev] dpdk config on VM
hi ,
The below error is because invalid coremask , your VM has only one core ,
but you are trying to assign eal option as -c 0xf that means you are
assigning 1,2,3,4 cores to dpdk application which are not available in your
VM .
you can increase sufficient number of cores while u launch virtual machine .
please check EAL options for dpdk before proceeding .
http://dpdk.org/doc/guides-16.04/testpmd_app_ug/run_app.html
On Wed, Jun 29, 2016 at 2:20 PM, Raja Jayapal wrote:
> Hi All,
>
> I have installed dpdk(16.04) on ubuntu VM and trying to run
> helloworld/testpmd application, but i am getting the below errors.
>
> root at host4-VirtualBox:/home/host4/dpdk/dpdk-16.04/examples/helloworld#
> echo $RTE_SDK
> /home/host4/dpdk/dpdk-16.04
> root at host4-VirtualBox:/home/host4/dpdk/dpdk-16.04/examples/helloworld#
> echo $RTE_TARGET
> x86_64-native-linuxapp-gcc
> root at host4-VirtualBox:/home/host4/dpdk/dpdk-16.04/examples/helloworld#
> ./build/helloworld -c f -n 4
> EAL: Detected lcore 0 as core 0 on socket 0
> EAL: Support maximum 128 logical core(s) by configuration.
> EAL: Detected 1 lcore(s)
> EAL: lcore 1 unavailable
> EAL: invalid coremask
>
> Usage: ./build/helloworld [options]
>
> EAL common options:
> -c COREMASK Hexadecimal bitmask of cores to run on
> -l CORELIST List of cores to run on
> The argument format is [-c2][,c3[-c4],...]
> where c1, c2, etc are core indexes between 0 and 128
> --lcores COREMAPMap lcore set to physical cpu set
> The argument format is
> '<lcores[@cpus]>[<,lcores[@cpus]>...]'
> lcores and cpus list are grouped by '(' and ')'
>
> root at host4-VirtualBox:/home/host4/dpdk/dpdk-16.04/app/test-pmd# ./testpmd
> -c 0xf -n 4 -- -i --portmask=0x1 --nb-cores=2
> EAL: Detected lcore 0 as core 0 on socket 0
> EAL: Support maximum 128 logical core(s) by configuration.
> EAL: Detected 1 lcore(s)
> EAL: lcore 1 unavailable
> EAL: invalid coremask
>
> Usage: ./testpmd [options]
>
> EAL common options:
> -c COREMASK Hexadecimal bitmask of cores to run on
> -l CORELIST List of cores to run on
> The argument format is [-c2][,c3[-c4],...]
> where c1, c2, etc are core indexes between 0 and 128
>
>
> I tried with the options provided in below thread, but getting same error.
> http://openvswitch.org/pipermail/discuss/2014-December/016007.html
>
> Please let me know what could be the cause?
>
> Thanks,
> Raja
>
>
> -Srinivasreddy R wrote: -
> To: Raja Jayapal
> From: Srinivasreddy R
> Date: 06/27/2016 07:03PM
> Cc: "dev at dpdk.org"
> Subject: Re: [dpdk-dev] dpdk config on VM
>
>
> hi,
> check with the below link .With little changes you can make it work for
> your use case .
>
> https://github.com/01org/dpdk-ovs/blob/development/docs/04_Sample_Configurations/02_Userspace-vHost.md
>
>
> On Mon, Jun 27, 2016 at 2:50 PM, Raja Jayapal
> wrote:
>
>> Hi All,
>>
>> I am tyrying to install dpdk on ubuntu and test the applications.
>> I have successfully installed dpdk on Host as per the instruction guide ,
>> but little bit confused on how to bind it with VM.
>>
>> VM1(TrafficGen)--Host(DPDK)--VM2(Receiver)
>>
>> Do we need to install ovs to test the flows for the above scenarios?.
>> I did search a lot, but didnt get clear idea like how to do config on VM
>> side.
>> Please point out some config/installation guide for the same.
>>
>>
>> Thanks in Advance,
>> Raja
>> =-=-=
>> Notice: The information contained in this e-mail
>> message and/or attachments to it may contain
>> confidential or privileged information. If you are
>> not the intended recipient, any dissemination, use,
>> review, distribution, printing or copying of the
>> information contained in this e-mail message
>> and/or attachments to it are strictly prohibited. If
>> you have received this communication in error,
>> please notify us by reply e-mail or telephone and
>> immediately and permanently delete the message
>> and any attachments. Thank you
>>
>>
>>
>
>
>
> Regards,
> srinivas.
>
--
regards
srinivas.
[dpdk-dev] dpdk config on VM
hi, check with the below link .With little changes you can make it work for your use case . https://github.com/01org/dpdk-ovs/blob/development/docs/04_Sample_Configurations/02_Userspace-vHost.md On Mon, Jun 27, 2016 at 2:50 PM, Raja Jayapal wrote: > Hi All, > > I am tyrying to install dpdk on ubuntu and test the applications. > I have successfully installed dpdk on Host as per the instruction guide , > but little bit confused on how to bind it with VM. > > VM1(TrafficGen)--Host(DPDK)--VM2(Receiver) > > Do we need to install ovs to test the flows for the above scenarios?. > I did search a lot, but didnt get clear idea like how to do config on VM > side. > Please point out some config/installation guide for the same. > > > Thanks in Advance, > Raja > =-=-= > Notice: The information contained in this e-mail > message and/or attachments to it may contain > confidential or privileged information. If you are > not the intended recipient, any dissemination, use, > review, distribution, printing or copying of the > information contained in this e-mail message > and/or attachments to it are strictly prohibited. If > you have received this communication in error, > please notify us by reply e-mail or telephone and > immediately and permanently delete the message > and any attachments. Thank you > > > Regards, srinivas.
[dpdk-dev] packet loss in usvhost dpdk interface
thanks a lot .. great help . On Wed, Apr 8, 2015 at 8:10 PM, Xie, Huawei wrote: > On 4/6/2015 6:42 PM, Srinivasreddy R wrote: > > Hi, > > I have observed packet loss with usvhost dpdk interfaces even at a very > > small rate . > > This is because virtqueue [dev->virtqueue] is found to be full, > > and my application should drop the packets . > Maybe your virtio guest is slow in processing the packets. > Could you refer to the retry mechanism in the vhost example? search > enable_retry in switch_worker in examples/vhost/main.c. > > > > some one pls help me , > > how can I avoid this loss . > > > > > > thanks > > srinivas. > > > > > >
[dpdk-dev] packet loss in usvhost dpdk interface
Hi, I have observed packet loss with usvhost dpdk interfaces even at a very small rate . This is because virtqueue [dev->virtqueue] is found to be full, and my application should drop the packets . some one pls help me , how can I avoid this loss . thanks srinivas.
[dpdk-dev] usvhost interface dropping packets
hi,
I am using usvhost interfaces for VM to VM communication with ovdk Version
1.2 .
when i am sending packets form one VM to another using PacketGen , i
observed packet drop .
the reason for this is , when packets are send in burst on vhost interface
it checks for the free entries in vhost_virtqueue .if the free enteries are
not available it retries and waits for some time . then the ovdk drops the
packets .
my question is :
How can i avoid packet drop .
i tried increasing retries and delay . it helped in reducing the loss but
not completely .
is there any solution for avoiding the drop . i have observed drop even at
a very less traffic .
am i missing any thing .
how can i proceed further .
the code part is :
FILE : *rte_port_vhost.c*
static inline uint32_t __attribute__((always_inline))
pf_vhost_enqueue_burst(struct virtio_net *dev, struct rte_mbuf **pkts,
unsigned count)
{
struct vhost_virtqueue *vq;
struct vring_desc *desc;
MODULE_DBG_LOG( "(%"PRIu64") virtio_dev_rx()\n", dev->device_fh);
vq = dev->virtqueue[VIRTIO_RXQ];
count = (count > PKT_BURST_SIZE) ? PKT_BURST_SIZE : count;
/* As many data cores may want access to available buffers, they need
to be reserved. */
do {
res_base_idx = vq->last_used_idx_res;
avail_idx = *((volatile uint16_t *)>avail->idx);
free_entries = (avail_idx - res_base_idx);
/* If retry is enabled and the queue is full then we wait and retry
to avoid packet loss. */
if (unlikely(count > free_entries)) {
for (retry = 0; retry < g_burst_tx_retry_num; retry++) {
rte_delay_us(g_burst_tx_delay_time);
avail_idx =
*((volatile uint16_t *)>avail->idx);
free_entries = (avail_idx - res_base_idx);
if (count <= free_entries)
break;
}
}
--
thanks
srinivas.
[dpdk-dev] [Dpdk-ovs] problem in binding interfaces of virtio-pci on the VM
hi , Thanks for your reply . Are you sure that esn3 is the device you are expecting to use to talk to the host? I am sure ens3 is the device i talk to the host . later on i removed ens3 and accessed my VM with "vncviewer" . when i bind interfaces on the VM with igb_uio . How the communication between guest to host takes place .. may be i am not handling properly on the host application . what are the things to be taken care in the host application ? thanks, srinivas. > Gary > > -Original Message- > From: Dpdk-ovs [mailto:dpdk-ovs-bounces at lists.01.org] On Behalf Of > Srinivasreddy R > Sent: Friday, February 27, 2015 06:00 > To: Bruce Richardson > Cc: dev at dpdk.org; dpdk-ovs at lists.01.org > Subject: Re: [Dpdk-ovs] [dpdk-dev] problem in binding interfaces of > virtio-pci on the VM > > hi , > > please fine the oputput On the VM . > > /tools/dpdk_nic_bind.py --status > > Network devices using DPDK-compatible driver > == == > > Network devices using kernel driver > === > :00:03.0 '82540EM Gigabit Ethernet Controller' if=ens3 drv=e1000 > unused=igb_uio *Active* > :00:04.0 'Virtio network device' if= drv=virtio-pci unused=igb_uio > :00:05.0 'Virtio network device' if= drv=virtio-pci unused=igb_uio > > Other network devices > = > > > > i am trying to bind "virtio network devices " with pci 00:04.0 , > 00:05.0 . > . > when i give the below command i face the issue. > ./dpdk_nic_bind.py --bind=igb_uio 00:04.0 00:05.0 > > > > when qemu does not able to allocate memory for vm on /dev/hugepages . > it gives the below error message . "Cannot allocate memory " > In this case i am able to bind the interfaces to igb_uio . > does this gives any hint on what wrong i am doing . > > do i need to handle any thing on the host when i bind to igb_uio on the > guest for usvhost . > > > ./x86_64-softmmu/qemu-system-x86_64 -cpu host -boot c -hda > /home/utils/images/vm1.img -m 4096M -smp 3 --enable-kvm -name 'VM1' > -nographic -vnc :1 -pidfile /tmp/vm1.pid -drive > file=fat:rw:/tmp/qemu_share,snapshot=off -monitor > unix:/tmp/vm1monitor,server,nowait -net none -no-reboot -mem-path > /dev/hugepages -mem-prealloc -netdev > type=tap,id=net1,script=no,downscript=no,ifname=usvhost1,vhost=on -device > virtio-net-pci,netdev=net1,mac=00:16:3e:00:03:03,csum=off,gso=off,guest_tso4=off,guest_tso6=off,guest_ecn=off > -netdev type=tap,id=net2,script=no,downscript=no,ifname=usvhost2,vhost=on > -device > > virtio-net-pci,netdev=net2,mac=00:16:3e:00:03:04,csum=off,gso=off,guest_tso4=off,guest_tso6=off,guest_ecn=off > -net nic -net tap,ifname=tap6,script=no > vvfat /tmp/qemu_share chs 1024,16,63 > file_ram_alloc: can't mmap RAM pages: Cannot allocate memory > qemu-system-x86_64: unable to start vhost net: 22: falling back on > userspace virtio > qemu-system-x86_64: unable to start vhost net: 22: falling back on > userspace virtio > > > > > thanks, > srinivas. > > > > On Fri, Feb 27, 2015 at 3:36 PM, Bruce Richardson < > bruce.richardson at intel.com> wrote: > > > On Thu, Feb 26, 2015 at 10:46:58PM +0530, Srinivasreddy R wrote: > > > hi Bruce , > > > Thank you for your response . > > > I am accessing my VM via " vncviewer " . so ssh doesn't come into > > picture . > > > Is there any way to find the root cause of my problem . does dpdk > > > stores any logs while binding interfaces to igb_uio. > > > i have seen my /var/log/messages . but could not find any clue. > > > > > > the movement i gave the below command my vm got struck and not > > > responding untill i forcefully kill the qemu and relaunch . > > > ./dpdk_nic_bind.py --bind=igb_uio 00:04.0 00:05.0 > > > > > > > Does VNC not also connect using a network port? What is the output of > > ./dpdk_nic_bind.py --status before you run this command? > > > > /Bruce > > > > > > > > > > > thanks, > > > srinivas. > > > > > > > > > > > > On Thu, Feb 26, 2015 at 10:30 PM, Bruce Richardson < > > > bruce.richardson at intel.com> wrote: > > > > > > > On Thu, Feb 26, 2015 at 10:08:59PM +0530, Srinivasreddy R wrote: > > > > > hi Mike, > > > > > Thanks for our detailed explanation of your example . usually i > > > > > do > > > > similar > > > > > to u and i am aware of working with dpdk applications . > > > > > my problem is : > > > > >
[dpdk-dev] [Dpdk-ovs] problem in binding interfaces of virtio-pci on the VM
hi , please fine the oputput On the VM . /tools/dpdk_nic_bind.py --status Network devices using DPDK-compatible driver == == Network devices using kernel driver === :00:03.0 '82540EM Gigabit Ethernet Controller' if=ens3 drv=e1000 unused=igb_uio *Active* :00:04.0 'Virtio network device' if= drv=virtio-pci unused=igb_uio :00:05.0 'Virtio network device' if= drv=virtio-pci unused=igb_uio Other network devices = i am trying to bind "virtio network devices " with pci 00:04.0 , 00:05.0 . . when i give the below command i face the issue. ./dpdk_nic_bind.py --bind=igb_uio 00:04.0 00:05.0 when qemu does not able to allocate memory for vm on /dev/hugepages . it gives the below error message . "Cannot allocate memory " In this case i am able to bind the interfaces to igb_uio . does this gives any hint on what wrong i am doing . do i need to handle any thing on the host when i bind to igb_uio on the guest for usvhost . ./x86_64-softmmu/qemu-system-x86_64 -cpu host -boot c -hda /home/utils/images/vm1.img -m 4096M -smp 3 --enable-kvm -name 'VM1' -nographic -vnc :1 -pidfile /tmp/vm1.pid -drive file=fat:rw:/tmp/qemu_share,snapshot=off -monitor unix:/tmp/vm1monitor,server,nowait -net none -no-reboot -mem-path /dev/hugepages -mem-prealloc -netdev type=tap,id=net1,script=no,downscript=no,ifname=usvhost1,vhost=on -device virtio-net-pci,netdev=net1,mac=00:16:3e:00:03:03,csum=off,gso=off,guest_tso4=off,guest_tso6=off,guest_ecn=off -netdev type=tap,id=net2,script=no,downscript=no,ifname=usvhost2,vhost=on -device virtio-net-pci,netdev=net2,mac=00:16:3e:00:03:04,csum=off,gso=off,guest_tso4=off,guest_tso6=off,guest_ecn=off -net nic -net tap,ifname=tap6,script=no vvfat /tmp/qemu_share chs 1024,16,63 file_ram_alloc: can't mmap RAM pages: Cannot allocate memory qemu-system-x86_64: unable to start vhost net: 22: falling back on userspace virtio qemu-system-x86_64: unable to start vhost net: 22: falling back on userspace virtio thanks, srinivas. On Fri, Feb 27, 2015 at 3:36 PM, Bruce Richardson < bruce.richardson at intel.com> wrote: > On Thu, Feb 26, 2015 at 10:46:58PM +0530, Srinivasreddy R wrote: > > hi Bruce , > > Thank you for your response . > > I am accessing my VM via " vncviewer " . so ssh doesn't come into > picture . > > Is there any way to find the root cause of my problem . does dpdk stores > > any logs while binding interfaces to igb_uio. > > i have seen my /var/log/messages . but could not find any clue. > > > > the movement i gave the below command my vm got struck and not responding > > untill i forcefully kill the qemu and relaunch . > > ./dpdk_nic_bind.py --bind=igb_uio 00:04.0 00:05.0 > > > > Does VNC not also connect using a network port? What is the output of > ./dpdk_nic_bind.py --status before you run this command? > > /Bruce > > > > > > > thanks, > > srinivas. > > > > > > > > On Thu, Feb 26, 2015 at 10:30 PM, Bruce Richardson < > > bruce.richardson at intel.com> wrote: > > > > > On Thu, Feb 26, 2015 at 10:08:59PM +0530, Srinivasreddy R wrote: > > > > hi Mike, > > > > Thanks for our detailed explanation of your example . usually i do > > > similar > > > > to u and i am aware of working with dpdk applications . > > > > my problem is : > > > > 1. i have written a code for host to guest communication .[taken > form > > > > usvhost which is developed in ovdk vswitch] . > > > > 2. i launched VM with two interfaces . > > > > 3. i am able to send and receive traffic to and from guest to host on > > > these > > > > interfaces . > > > > 4. when i try to bind these interfaces to igb_uio to run dpdk > > > application > > > > . i am not able to access my instance . it got struck and not > responding > > > . > > > > i need to hard reboot the vm. > > > > > > Are you sure you are not trying to access the vm via one of the > interfaces > > > now bount to igb_uio? If you bind the interface you use for ssh to > igb_uio, > > > you won't be able to ssh to that vm any more. > > > > > > /Bruce > > > > > > > > > > > My Question is : > > > > surely i might done something wrong in code . as my VM is not able to > > > > access any more when i try to bind interfaces to igb_uio . not able > to > > > > debug the issue . > > > > someone please help me in figuring the issue . i dont find anything > in > > > > /var/log/messages after relaunching the instance . &
[dpdk-dev] [Dpdk-ovs] problem in binding interfaces of virtio-pci on the VM
hi Bruce , Thank you for your response . I am accessing my VM via " vncviewer " . so ssh doesn't come into picture . Is there any way to find the root cause of my problem . does dpdk stores any logs while binding interfaces to igb_uio. i have seen my /var/log/messages . but could not find any clue. the movement i gave the below command my vm got struck and not responding untill i forcefully kill the qemu and relaunch . ./dpdk_nic_bind.py --bind=igb_uio 00:04.0 00:05.0 thanks, srinivas. On Thu, Feb 26, 2015 at 10:30 PM, Bruce Richardson < bruce.richardson at intel.com> wrote: > On Thu, Feb 26, 2015 at 10:08:59PM +0530, Srinivasreddy R wrote: > > hi Mike, > > Thanks for our detailed explanation of your example . usually i do > similar > > to u and i am aware of working with dpdk applications . > > my problem is : > > 1. i have written a code for host to guest communication .[taken form > > usvhost which is developed in ovdk vswitch] . > > 2. i launched VM with two interfaces . > > 3. i am able to send and receive traffic to and from guest to host on > these > > interfaces . > > 4. when i try to bind these interfaces to igb_uio to run dpdk > application > > . i am not able to access my instance . it got struck and not responding > . > > i need to hard reboot the vm. > > Are you sure you are not trying to access the vm via one of the interfaces > now bount to igb_uio? If you bind the interface you use for ssh to igb_uio, > you won't be able to ssh to that vm any more. > > /Bruce > > > > > My Question is : > > surely i might done something wrong in code . as my VM is not able to > > access any more when i try to bind interfaces to igb_uio . not able to > > debug the issue . > > someone please help me in figuring the issue . i dont find anything in > > /var/log/messages after relaunching the instance . > > > > > > thanks, > > srinivas. > > > > > > > > On Thu, Feb 26, 2015 at 8:42 PM, Polehn, Mike A > > > wrote: > > > > > In this example, the control network 00:03.0, remains unbound to UIO > > > driver but remains attached > > > to Linux device driver (ssh access with putty) and just the target > > > interfaces are bound. > > > Below, it shows all 3 interfaces bound to the uio driver, which are not > > > usable until a task uses the UIO driver. > > > > > > [root at F21vm l3fwd-vf]# lspci -nn > > > 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC > [Natoma] > > > [8086:1237] (rev 02) > > > 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA > > > [Natoma/Triton II] [8086:7000] > > > 00:01.1 IDE interface [0101]: Intel Corporation 82371SB PIIX3 IDE > > > [Natoma/Triton II] [8086:7010] > > > 00:01.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI > > > [8086:7113] (rev 03) > > > 00:02.0 VGA compatible controller [0300]: Cirrus Logic GD 5446 > [1013:00b8] > > > 00:03.0 Ethernet controller [0200]: Red Hat, Inc Virtio network device > > > [1af4:1000] > > > 00:04.0 Ethernet controller [0200]: Intel Corporation XL710/X710 > Virtual > > > Function [8086:154c] (rev 01) > > > 00:05.0 Ethernet controller [0200]: Intel Corporation XL710/X710 > Virtual > > > Function [8086:154c] (rev 01) > > > > > > [root at F21vm l3fwd-vf]# /usr/src/dpdk/tools/dpdk_nic_bind.py > > > --bind=igb_uio 00:04.0 > > > [root at F21vm l3fwd-vf]# /usr/src/dpdk/tools/dpdk_nic_bind.py > > > --bind=igb_uio 00:05.0 > > > [root at F21vm l3fwd-vf]# /usr/src/dpdk/tools/dpdk_nic_bind.py --status > > > > > > Network devices using DPDK-compatible driver > > > > > > :00:04.0 'XL710/X710 Virtual Function' drv=igb_uio unused=i40evf > > > :00:05.0 'XL710/X710 Virtual Function' drv=igb_uio unused=i40evf > > > > > > Network devices using kernel driver > > > === > > > :00:03.0 'Virtio network device' if= drv=virtio-pci > > > unused=virtio_pci,igb_uio > > > > > > Other network devices > > > = > > > > > > > > > -Original Message- > > > From: Dpdk-ovs [mailto:dpdk-ovs-bounces at lists.01.org] On Behalf Of > > > Srinivasreddy R > > > Sent: Thursday, February 26, 2015 6:11 AM > > > To: dev at dpdk.org; dpdk-ovs at lists.01.org > > > Subject: [Dpdk-ovs] problem in binding interfaces of virtio-pci on the > VM > > >
[dpdk-dev] [Dpdk-ovs] problem in binding interfaces of virtio-pci on the VM
hi Mike, Thanks for our detailed explanation of your example . usually i do similar to u and i am aware of working with dpdk applications . my problem is : 1. i have written a code for host to guest communication .[taken form usvhost which is developed in ovdk vswitch] . 2. i launched VM with two interfaces . 3. i am able to send and receive traffic to and from guest to host on these interfaces . 4. when i try to bind these interfaces to igb_uio to run dpdk application . i am not able to access my instance . it got struck and not responding . i need to hard reboot the vm. My Question is : surely i might done something wrong in code . as my VM is not able to access any more when i try to bind interfaces to igb_uio . not able to debug the issue . someone please help me in figuring the issue . i dont find anything in /var/log/messages after relaunching the instance . thanks, srinivas. On Thu, Feb 26, 2015 at 8:42 PM, Polehn, Mike A wrote: > In this example, the control network 00:03.0, remains unbound to UIO > driver but remains attached > to Linux device driver (ssh access with putty) and just the target > interfaces are bound. > Below, it shows all 3 interfaces bound to the uio driver, which are not > usable until a task uses the UIO driver. > > [root at F21vm l3fwd-vf]# lspci -nn > 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] > [8086:1237] (rev 02) > 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA > [Natoma/Triton II] [8086:7000] > 00:01.1 IDE interface [0101]: Intel Corporation 82371SB PIIX3 IDE > [Natoma/Triton II] [8086:7010] > 00:01.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI > [8086:7113] (rev 03) > 00:02.0 VGA compatible controller [0300]: Cirrus Logic GD 5446 [1013:00b8] > 00:03.0 Ethernet controller [0200]: Red Hat, Inc Virtio network device > [1af4:1000] > 00:04.0 Ethernet controller [0200]: Intel Corporation XL710/X710 Virtual > Function [8086:154c] (rev 01) > 00:05.0 Ethernet controller [0200]: Intel Corporation XL710/X710 Virtual > Function [8086:154c] (rev 01) > > [root at F21vm l3fwd-vf]# /usr/src/dpdk/tools/dpdk_nic_bind.py > --bind=igb_uio 00:04.0 > [root at F21vm l3fwd-vf]# /usr/src/dpdk/tools/dpdk_nic_bind.py > --bind=igb_uio 00:05.0 > [root at F21vm l3fwd-vf]# /usr/src/dpdk/tools/dpdk_nic_bind.py --status > > Network devices using DPDK-compatible driver > > :00:04.0 'XL710/X710 Virtual Function' drv=igb_uio unused=i40evf > :00:05.0 'XL710/X710 Virtual Function' drv=igb_uio unused=i40evf > > Network devices using kernel driver > === > :00:03.0 'Virtio network device' if= drv=virtio-pci > unused=virtio_pci,igb_uio > > Other network devices > ===== > > > -Original Message- > From: Dpdk-ovs [mailto:dpdk-ovs-bounces at lists.01.org] On Behalf Of > Srinivasreddy R > Sent: Thursday, February 26, 2015 6:11 AM > To: dev at dpdk.org; dpdk-ovs at lists.01.org > Subject: [Dpdk-ovs] problem in binding interfaces of virtio-pci on the VM > > hi , > I have written sample program for usvhost supported by ovdk. > > i have initialized VM using the below command . > On the VM : > > I am able to see two interfaces . and working fine with traffic in > rawsocket mode . > my problem is when i bind the interfaces to pmd driver[ ibg_uio ] my > virtual machine is getting hanged . and i am not able to access it further > . > now my question is . what may be the reason for the behavior . and how can > in debug the root cause . > please help in finding out the problem . > > > > ./tools/dpdk_nic_bind.py --status > > Network devices using DPDK-compatible driver > > > > Network devices using kernel driver > === > :00:03.0 '82540EM Gigabit Ethernet Controller' if=ens3 drv=e1000 > unused=igb_uio *Active* > :00:04.0 'Virtio network device' if= drv=virtio-pci unused=igb_uio > :00:05.0 'Virtio network device' if= drv=virtio-pci unused=igb_uio > > Other network devices > = > > > > ./dpdk_nic_bind.py --bind=igb_uio 00:04.0 00:05.0 > > > > ./x86_64-softmmu/qemu-system-x86_64 -cpu host -boot c -hda > /home/utils/images/vm1.img -m 2048M -smp 3 --enable-kvm -name 'VM1' > -nographic -vnc :1 -pidfile /tmp/vm1.pid -drive > file=fat:rw:/tmp/qemu_share,snapshot=off -monitor > unix:/tmp/vm1monitor,server,nowait -net none -no-reboot -mem-path > /dev/hugepages -mem-prealloc -netdev > type=tap,id=net1,script=no,downscript=no,ifname=usvhost1,vhost=on -device > virtio-net-pci,netdev=net1,mac=00:16:3e:00:03:03,csum=of
[dpdk-dev] problem in binding interfaces of virtio-pci on the VM
hi , I have written sample program for usvhost supported by ovdk. i have initialized VM using the below command . On the VM : I am able to see two interfaces . and working fine with traffic in rawsocket mode . my problem is when i bind the interfaces to pmd driver[ ibg_uio ] my virtual machine is getting hanged . and i am not able to access it further . now my question is . what may be the reason for the behavior . and how can in debug the root cause . please help in finding out the problem . ./tools/dpdk_nic_bind.py --status Network devices using DPDK-compatible driver Network devices using kernel driver === :00:03.0 '82540EM Gigabit Ethernet Controller' if=ens3 drv=e1000 unused=igb_uio *Active* :00:04.0 'Virtio network device' if= drv=virtio-pci unused=igb_uio :00:05.0 'Virtio network device' if= drv=virtio-pci unused=igb_uio Other network devices = ./dpdk_nic_bind.py --bind=igb_uio 00:04.0 00:05.0 ./x86_64-softmmu/qemu-system-x86_64 -cpu host -boot c -hda /home/utils/images/vm1.img -m 2048M -smp 3 --enable-kvm -name 'VM1' -nographic -vnc :1 -pidfile /tmp/vm1.pid -drive file=fat:rw:/tmp/qemu_share,snapshot=off -monitor unix:/tmp/vm1monitor,server,nowait -net none -no-reboot -mem-path /dev/hugepages -mem-prealloc -netdev type=tap,id=net1,script=no,downscript=no,ifname=usvhost1,vhost=on -device virtio-net-pci,netdev=net1,mac=00:16:3e:00:03:03,csum=off,gso=off,guest_tso4=off,guest_tso6=off,guest_ecn=off -netdev type=tap,id=net2,script=no,downscript=no,ifname=usvhost2,vhost=on -device virtio-net-pci,netdev=net2,mac=00:16:3e:00:03:04,csum=off,gso=off,guest_tso4=off,guest_tso6=off,guest_ecn=off -- thanks srinivas.
[dpdk-dev] [discuss]emulated e1000 device with qemu is not showing nic stats correctly
Hi , I have emulated virtual e1000 device using qemu . I have binded to igb_uio . and run PacketGen . Now I am able to receive and transmit packets on the device . But PacketGen is not showing Tx/Rx Rate . I have put printed struct rte_eth_stats after fetching nic stats . except tx, rx packet count all the other fields are zeroes . I am facing the same issue with my dpdk application . Is it a bug / known issue ? . I have used dpdk1.7. Have any faced it earlier . qemu: qemu-system-x86_64 -device e1000 .. on the VM : # lspci 00.03.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller (rev 03) my dpdk app eal_inti : EAL: core 1 is ready (tid=2b7fe700) EAL: PCI device .00.03.0 on NUMA socket -1 EAL: probe driver: 8086:100e rte_em_pmd EAL: PCI memory mapped at 0x7f602c96e000 dpdk_nic_bind.py --status Network devices using DPDK-compatible driver :00:03:0 '82540EM Gigabit Ethernet controller' drv=igb_uio unused= Thanks Srinivas.
[dpdk-dev] [DISCUSSION] : ERROR while running vhost example in dpdk-1.8
hi, May be I am missing something regarding hugetlbfs . I performed below steps for hugetlbfs . I am running on Ubuntu 14.04.1 LTS. cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=628ff32b-dede-4b47-bd13-893c13c18d00 ro quiet splash hugepagesz=2M hugepages=512 default_hugepagesz=1G hugepagesz=1G hugepages=8 vt.handoff=7 mount -t hugetlbfs nodev /mnt/huge echo 512 > /sys/kernel/mm/hugepages/hugepages-2048kB/ nr_hugepages mount -t hugetlbfs nodev /mnt/huge -o pagesize=2M thanks , Srinivas. On Fri, Jan 30, 2015 at 11:19 AM, Srinivasreddy R < srinivasreddy4390 at gmail.com> wrote: > thanks for your reply . even I face the same issue .any pointers to > proceed .. > > > ./build/app/vhost-switch -c f -n 4 -- -p 0x1 --dev-basename usvhost-1 > --stats 2 > EAL: Detected lcore 0 as core 0 on socket 0 > EAL: Detected lcore 1 as core 1 on socket 0 > EAL: Detected lcore 2 as core 2 on socket 0 > EAL: Detected lcore 3 as core 3 on socket 0 > EAL: Detected lcore 4 as core 0 on socket 0 > EAL: Detected lcore 5 as core 1 on socket 0 > EAL: Detected lcore 6 as core 2 on socket 0 > EAL: Detected lcore 7 as core 3 on socket 0 > EAL: Support maximum 128 logical core(s) by configuration. > EAL: Detected 8 lcore(s) > EAL: cannot open VFIO container, error 2 (No such file or directory) > EAL: VFIO support could not be initialized > EAL: Setting up memory... > EAL: Ask a virtual area of 0x2 bytes > EAL: Virtual area found at 0x7fb6c000 (size = 0x2) > EAL: Ask a virtual area of 0x1a0 bytes > EAL: Virtual area found at 0x7fb8f560 (size = 0x1a0) > EAL: Ask a virtual area of 0x20 bytes > EAL: Virtual area found at 0x7fb8f520 (size = 0x20) > EAL: Ask a virtual area of 0x20 bytes > EAL: Virtual area found at 0x7fb8f4e0 (size = 0x20) > EAL: Ask a virtual area of 0x6c0 bytes > EAL: Virtual area found at 0x7fb8ee00 (size = 0x6c0) > EAL: Ask a virtual area of 0x20 bytes > EAL: Virtual area found at 0x7fb8edc0 (size = 0x20) > EAL: Ask a virtual area of 0x20 bytes > EAL: Virtual area found at 0x7fb8ed80 (size = 0x20) > EAL: Ask a virtual area of 0x20 bytes > EAL: Virtual area found at 0x7fb8ed40 (size = 0x20) > EAL: Ask a virtual area of 0x9e0 bytes > EAL: Virtual area found at 0x7fb8e340 (size = 0x9e0) > EAL: Ask a virtual area of 0x1900 bytes > EAL: Virtual area found at 0x7fb8ca20 (size = 0x1900) > EAL: Ask a virtual area of 0x20 bytes > EAL: Virtual area found at 0x7fb8c9e0 (size = 0x20) > EAL: Ask a virtual area of 0x20 bytes > EAL: Virtual area found at 0x7fb8c9a0 (size = 0x20) > EAL: Ask a virtual area of 0x1000 bytes > EAL: Virtual area found at 0x7fb6afe0 (size = 0x1000) > EAL: Ask a virtual area of 0x3c0 bytes > EAL: Virtual area found at 0x7fb8c5c0 (size = 0x3c0) > EAL: Ask a virtual area of 0x20 bytes > EAL: Virtual area found at 0x7fb8c580 (size = 0x20) > EAL: Requesting 8 pages of size 1024MB from socket 0 > EAL: Requesting 512 pages of size 2MB from socket 0 > EAL: TSC frequency is ~3092840 KHz > EAL: Master core 0 is ready (tid=f83c0880) > PMD: ENICPMD trace: rte_enic_pmd_init > EAL: Core 3 is ready (tid=c3ded700) > EAL: Core 2 is ready (tid=c45ee700) > EAL: Core 1 is ready (tid=c4def700) > EAL: PCI device :01:00.0 on NUMA socket -1 > EAL: probe driver: 8086:1521 rte_igb_pmd > EAL: PCI memory mapped at 0x7fb8f700 > EAL: PCI memory mapped at 0x7fb8f710 > PMD: eth_igb_dev_init(): port_id 0 vendorID=0x8086 deviceID=0x1521 > EAL: PCI device :01:00.1 on NUMA socket -1 > EAL: probe driver: 8086:1521 rte_igb_pmd > EAL: :01:00.1 not managed by UIO driver, skipping > EAL: PCI device :03:00.0 on NUMA socket -1 > EAL: probe driver: 8086:10d3 rte_em_pmd > EAL: :03:00.0 not managed by UIO driver, skipping > EAL: PCI device :04:00.0 on NUMA socket -1 > EAL: probe driver: 8086:10d3 rte_em_pmd > EAL: :04:00.0 not managed by UIO driver, skipping > pf queue num: 0, configured vmdq pool num: 8, each vmdq pool has 1 queues > PMD: eth_igb_rx_queue_setup(): sw_ring=0x7fb8f60f7e00 > hw_ring=0x7fb8f5228580 dma_addr=0x36628580 > PMD: eth_igb_rx_queue_setup(): sw_ring=0x7fb8f60f5d00 > hw_ring=0x7fb8f5238580 dma_addr=0x36638580 > PMD: eth_igb_rx_queue_setup(): sw_ring=0x7fb8f60f3c00 > hw_ring=0x7fb8f5248580 dma_addr=0x36648580 > PMD: eth_igb_rx_queue_setup(): sw_ring=0x7fb8f60f1b00 > hw_ring=0x7fb8f5258580 dma_addr=0x36658580 > PMD: eth_igb_rx_queue_setup(): sw_ring=0x7fb8f60efa00 > hw_ring=0x7fb8f5268580 dma_addr=0x36668580 > PMD: eth_igb_rx_queue_setup(): sw_ring=0x7fb8f60ed900 > hw_ring=0x7fb8f5278580 dma_addr=0x366
[dpdk-dev] [DISCUSSION] : ERROR while running vhost example in dpdk-1.8
dma_addr=0x366d8580 PMD: eth_igb_start(): << VHOST_PORT: Max virtio devices supported: 8 VHOST_PORT: Port 0 MAC: 2c 53 4a 00 28 68 VHOST_DATA: Procesing on Core 1 started VHOST_DATA: Procesing on Core 2 started VHOST_DATA: Procesing on Core 3 started Device statistics == VHOST_CONFIG: (0) Device configuration started VHOST_CONFIG: (0) Failed to find memory file for pid 845 Device statistics ./qemu-wrap.py -machine pc-i440fx-1.4,accel=kvm,usb=off -cpu host -smp 2,sockets=2,cores=1,threads=1 -netdev tap,id=hostnet1,vhost=on -device virtio-net-pci,netdev=hostnet1,id=net1 -hda /home/utils/images/vm1.img -m 2048 -vnc 0.0.0.0:2 -net nic -net tap,ifname=tap3,script=no -mem-path /dev/hugepages -mem-prealloc W: /etc/qemu-ifup: no bridge for guest interface found file_ram_alloc: can't mmap RAM pages: Cannot allocate memory qemu-system-x86_64: unable to start vhost net: 22: falling back on userspace virtio mount | grep huge cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,relatime,hugetlb) nodev on /dev/hugepages type hugetlbfs (rw) nodev on /mnt/huge type hugetlbfs (rw,pagesize=2M) cat /proc/meminfo MemTotal: 16345340 kB MemFree: 4591596 kB Buffers: 466472 kB Cached: 1218728 kB SwapCached:0 kB Active: 1147228 kB Inactive: 762992 kB Active(anon): 232732 kB Inactive(anon):14760 kB Active(file): 914496 kB Inactive(file): 748232 kB Unevictable:3704 kB Mlocked:3704 kB SwapTotal: 16686076 kB SwapFree: 16686076 kB Dirty: 488 kB Writeback: 0 kB AnonPages:230800 kB Mapped:55248 kB Shmem: 17932 kB Slab: 245116 kB SReclaimable: 214372 kB SUnreclaim:30744 kB KernelStack:3664 kB PageTables:13900 kB NFS_Unstable: 0 kB Bounce:0 kB WritebackTmp: 0 kB CommitLimit:20140152 kB Committed_AS:1489760 kB VmallocTotal: 34359738367 kB VmallocUsed: 374048 kB VmallocChunk: 34359356412 kB HardwareCorrupted: 0 kB AnonHugePages:106496 kB HugePages_Total: 8 HugePages_Free:0 HugePages_Rsvd:0 HugePages_Surp:0 Hugepagesize:1048576 kB DirectMap4k: 91600 kB DirectMap2M: 2965504 kB DirectMap1G:13631488 kB sysctl -A | grep huge vm.hugepages_treat_as_movable = 0 vm.hugetlb_shm_group = 0 vm.nr_hugepages = 8 vm.nr_hugepages_mempolicy = 8 vm.nr_overcommit_hugepages = 0 thanks Srinivas. On Fri, Jan 30, 2015 at 10:59 AM, Linhaifeng wrote: > > > On 2015/1/30 0:48, Srinivasreddy R wrote: > > EAL: 512 hugepages of size 2097152 reserved, but no mounted hugetlbfs > found > > for that size > > Maybe you haven't mount hugetlbfs. > -- > Regards, > Haifeng > > -- thanks srinivas.
[dpdk-dev] [DISCUSSION] : ERROR while running vhost example in dpdk-1.8
Hi, I am using dpdk-1.8.0. I am trying to run vhost example . I followed sample app user guide at below link. http://www.dpdk.org/doc/guides/sample_app_ug/vhost.html what may be the reason . may be I am missing some thing . Facing problem while running , VHOST_CONFIG: (0) Failed to find memory file for pid 5235 file_ram_alloc: can't mmap RAM pages: Cannot allocate memory qemu-system-x86_64: unable to start vhost net: 22: falling back on userspace virtio Vhost switch app : /home/utils/dpdk-1.8.0/examples/vhost# ./build/app/vhost-switch -c f -n 4 -- -p 0x1--dev-basename usvhost-1 --stats 2 EAL: Detected lcore 0 as core 0 on socket 0 EAL: Detected lcore 1 as core 1 on socket 0 EAL: Detected lcore 2 as core 2 on socket 0 EAL: Detected lcore 3 as core 3 on socket 0 EAL: Detected lcore 4 as core 0 on socket 0 EAL: Detected lcore 5 as core 1 on socket 0 EAL: Detected lcore 6 as core 2 on socket 0 EAL: Detected lcore 7 as core 3 on socket 0 EAL: Support maximum 128 logical core(s) by configuration. EAL: Detected 8 lcore(s) EAL: 512 hugepages of size 2097152 reserved, but no mounted hugetlbfs found for that size EAL: cannot open VFIO container, error 2 (No such file or directory) EAL: VFIO support could not be initialized EAL: Setting up memory... EAL: Ask a virtual area of 0x2 bytes EAL: Virtual area found at 0x7f89c000 (size = 0x2) EAL: Requesting 8 pages of size 1024MB from socket 0 EAL: TSC frequency is ~3092841 KHz EAL: Master core 0 is ready (tid=f500d880) PMD: ENICPMD trace: rte_enic_pmd_init EAL: Core 3 is ready (tid=f26e5700) EAL: Core 2 is ready (tid=f2ee6700) EAL: Core 1 is ready (tid=f36e7700) EAL: PCI device :01:00.0 on NUMA socket -1 EAL: probe driver: 8086:1521 rte_igb_pmd EAL: PCI memory mapped at 0x7f8bc000 EAL: PCI memory mapped at 0x7f8bc010 PMD: eth_igb_dev_init(): port_id 0 vendorID=0x8086 deviceID=0x1521 EAL: PCI device :01:00.1 on NUMA socket -1 EAL: probe driver: 8086:1521 rte_igb_pmd EAL: :01:00.1 not managed by UIO driver, skipping EAL: PCI device :03:00.0 on NUMA socket -1 EAL: probe driver: 8086:10d3 rte_em_pmd EAL: :03:00.0 not managed by UIO driver, skipping EAL: PCI device :04:00.0 on NUMA socket -1 EAL: probe driver: 8086:10d3 rte_em_pmd EAL: :04:00.0 not managed by UIO driver, skipping pf queue num: 0, configured vmdq pool num: 8, each vmdq pool has 1 queues PMD: eth_igb_rx_queue_setup(): sw_ring=0x7f89c0af7e00 hw_ring=0x7f8a0bbc2000 dma_addr=0x24bbc2000 PMD: eth_igb_rx_queue_setup(): sw_ring=0x7f89c0af5d00 hw_ring=0x7f8a0bbd2000 dma_addr=0x24bbd2000 PMD: eth_igb_rx_queue_setup(): sw_ring=0x7f89c0af3c00 hw_ring=0x7f8a0bbe2000 dma_addr=0x24bbe2000 PMD: eth_igb_rx_queue_setup(): sw_ring=0x7f89c0af1b00 hw_ring=0x7f8a0bbf2000 dma_addr=0x24bbf2000 PMD: eth_igb_rx_queue_setup(): sw_ring=0x7f89c0aefa00 hw_ring=0x7f8a0bc02000 dma_addr=0x24bc02000 PMD: eth_igb_rx_queue_setup(): sw_ring=0x7f89c0aed900 hw_ring=0x7f8a0bc12000 dma_addr=0x24bc12000 PMD: eth_igb_rx_queue_setup(): sw_ring=0x7f89c0aeb800 hw_ring=0x7f8a0bc22000 dma_addr=0x24bc22000 PMD: eth_igb_rx_queue_setup(): sw_ring=0x7f89c0ae9700 hw_ring=0x7f8a0bc32000 dma_addr=0x24bc32000 PMD: eth_igb_tx_queue_setup(): To improve 1G driver performance, consider setting the TX WTHRESH value to 4, 8, or 16. PMD: eth_igb_tx_queue_setup(): sw_ring=0x7f89c0ae7600 hw_ring=0x7f8a0bc42000 dma_addr=0x24bc42000 PMD: eth_igb_tx_queue_setup(): To improve 1G driver performance, consider setting the TX WTHRESH value to 4, 8, or 16. PMD: eth_igb_tx_queue_setup(): sw_ring=0x7f89c0ae5500 hw_ring=0x7f8a0bc52000 dma_addr=0x24bc52000 PMD: eth_igb_tx_queue_setup(): To improve 1G driver performance, consider setting the TX WTHRESH value to 4, 8, or 16. PMD: eth_igb_tx_queue_setup(): sw_ring=0x7f89c0ae3400 hw_ring=0x7f8a0bc62000 dma_addr=0x24bc62000 PMD: eth_igb_tx_queue_setup(): To improve 1G driver performance, consider setting the TX WTHRESH value to 4, 8, or 16. PMD: eth_igb_tx_queue_setup(): sw_ring=0x7f89c0ae1300 hw_ring=0x7f8a0bc72000 dma_addr=0x24bc72000 PMD: eth_igb_start(): << VHOST_PORT: Max virtio devices supported: 8 VHOST_PORT: Port 0 MAC: 2c 53 4a 00 28 68 VHOST_DATA: Procesing on Core 1 started VHOST_DATA: Procesing on Core 2 started VHOST_DATA: Procesing on Core 3 started Device statistics == VHOST_CONFIG: (0) Device configuration started Device statistics == VHOST_CONFIG: (0) Failed to find memory file for pid 5235 Device statistics == Qemu : ./qemu-wrap.py -machine pc-i440fx-1.4,accel=kvm,usb=off -cpu host -smp 2,sockets=2,cores=1,threads=1 -netdev tap,id=hostnet1,vhost=on -device
[dpdk-dev] [DISCUSSION] : ERROR while compiling dpdk-1.7 on ubuntu14.04
hi, math library -lm is included . gcc -m64 -pthread -fPIC -march=native -DRTE_MACHINE_CPUFLAG_SSE -DRTE_MACHINE_CPUFLAG_SSE2 -DRTE_MACHINE_CPUFLAG_SSE3 -DRTE_MACHINE_CPUFLAG_SSSE3 -DRTE_MACHINE_CPUFLAG_SSE4_1 -DRTE_MACHINE_CPUFLAG_SSE4_2 -DRTE_MACHINE_CPUFLAG_AES -DRTE_MACHINE_CPUFLAG_PCLMULQDQ -DRTE_MACHINE_CPUFLAG_AVX -DRTE_MACHINE_CPUFLAG_RDRAND -DRTE_MACHINE_CPUFLAG_FSGSBASE -DRTE_MACHINE_CPUFLAG_F16C -DRTE_MACHINE_CPUFLAG_AVX2 -DRTE_COMPILE_TIME_CPUFLAGS=RTE_CPUFLAG_SSE,RTE_CPUFLAG_SSE2,RTE_CPUFLAG_SSE3,RTE_CPUFLAG_SSSE3,RTE_CPUFLAG_SSE4_1,RTE_CPUFLAG_SSE4_2,RTE_CPUFLAG_AES,RTE_CPUFLAG_PCLMULQDQ,RTE_CPUFLAG_AVX,RTE_CPUFLAG_RDRAND,RTE_CPUFLAG_FSGSBASE,RTE_CPUFLAG_F16C,RTE_CPUFLAG_AVX2 -I/home/srini/dpdk-1.7.1/x86_64-ivshmem-linuxapp-gcc/include -include /home/srini/dpdk-1.7.1/x86_64-ivshmem-linuxapp-gcc/include/rte_config.h -W -Wall -Werror -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wold-style-definition -Wpointer-arith -Wcast-align -Wnested-externs -Wcast-qual -Wformat-nonliteral -Wformat-security -Wundef -Wwrite-strings -Wl,-Map=testacl.map,--cref -o testacl main.o -Wl,-export-dynamic -L/home/srini/dpdk-1.7.1/x86_64-ivshmem-linuxapp-gcc/lib -L/home/srini/dpdk-1.7.1/x86_64-ivshmem-linuxapp-gcc/lib -Wl,--whole-archive -Wl,-lrte_distributor -Wl,-lrte_kni -Wl,-lrte_ivshmem -Wl,-lrte_pipeline -Wl,-lrte_table -Wl,-lrte_port -Wl,-lrte_timer -Wl,-lrte_hash -Wl,-lrte_lpm -Wl,-lrte_power -Wl,-lrte_acl -Wl,-lrte_meter -Wl,-lrte_sched -Wl,-lm -Wl,-lrt -Wl,--start-group -Wl,-lrte_kvargs -Wl,-lrte_mbuf -Wl,-lrte_ip_frag -Wl,-lethdev -Wl,-lrte_malloc -Wl,-lrte_mempool -Wl,-lrte_ring -Wl,-lrte_eal -Wl,-lrte_cmdline -Wl,-lrte_cfgfile -Wl,-lrte_pmd_bond -Wl,-lrt -Wl,-lm -Wl,-lgcc_s -Wl,-ldl -Wl,--end-group -Wl,--no-whole-archive -Wl,-lintel_dpdk /home/srini/dpdk-1.7.1/x86_64-ivshmem-linuxapp-gcc/lib/libintel_dpdk.so: undefined reference to `log2' /home/srini/dpdk-1.7.1/x86_64-ivshmem-linuxapp-gcc/lib/libintel_dpdk.so: undefined reference to `ceil' /home/srini/dpdk-1.7.1/x86_64-ivshmem-linuxapp-gcc/lib/libintel_dpdk.so: undefined reference to `pow' /home/srini/dpdk-1.7.1/x86_64-ivshmem-linuxapp-gcc/lib/libintel_dpdk.so: undefined reference to `round' complete logs are pasted at : http://paste.ubuntu.com/9765779/ current ovs dpdk supports only dpdk-1.7.1. so i was forced to use dpdk-1.7 I have seen a patch for similar error but it is for dpdk-1.9.1 release http://dpdk.org/dev/patchwork/patch/716/ How can I solve this error . thanks, srinivas. On Sat, Jan 17, 2015 at 2:37 AM, Wiles, Keith wrote: > On 1/16/15, 7:43 AM, "Srinivasreddy R" > wrote: > > >sorry typo i am using Ubuntu 14.04.1 LTS . > > > >On Fri, Jan 16, 2015 at 7:06 PM, Srinivasreddy R < > >srinivasreddy4390 at gmail.com> wrote: > > > >> hi, > >> Getting error while compiling dpdk on ubuntu10.04. > >> > >> > >> export RTE_SDK=$(pwd) > >> export RTE_TARGET="x86_64-ivshmem-linuxapp-gcc" > >> > >> make CONFIG_RTE_BUILD_COMBINE_LIBS=y CONFIG_RTE_BUILD_SHARED_LIB=y > >>install > >> T="$RTE_TARGET" > > Check to make sure you are linking in the math lib -lm you can add a V=1 > to the command line and see the linker lines. > > > > >> > >> > >> == Build app/test-acl > >> CC main.o > >> LD testacl > >> /home/DPDK/dpdk-1.7.1/x86_64-ivshmem-linuxapp-gcc/lib/libintel_dpdk.so: > >> undefined reference to `log2' > >> /home/DPDK/dpdk-1.7.1/x86_64-ivshmem-linuxapp-gcc/lib/libintel_dpdk.so: > >> undefined reference to `ceil' > >> /home/DPDK/dpdk-1.7.1/x86_64-ivshmem-linuxapp-gcc/lib/libintel_dpdk.so: > >> undefined reference to `pow' > >> /home/DPDK/dpdk-1.7.1/x86_64-ivshmem-linuxapp-gcc/lib/libintel_dpdk.so: > >> undefined reference to `round' > >> collect2: error: ld returned 1 exit status > >> make[5]: *** [testacl] Error 1 > >> make[4]: *** [test-acl] Error 2 > >> make[3]: *** [app] Error 2 > >> make[2]: *** [all] Error 2 > >> make[1]: *** [x86_64-ivshmem-linuxapp-gcc_install] Error 2 > >> make: *** [install] Error 2 > >> > >> Following installation procedure at link : > >> > >> > >> > https://github.com/01org/dpdk-ovs/blob/development/docs/01_Installation.m > >>d#dpdk > >> > >> > >> thanks > >> srinivas. > >> > > -- thanks srinivas.
[dpdk-dev] [DISCUSSION] : ERROR while compiling dpdk-1.7 on ubuntu14.04
sorry typo i am using Ubuntu 14.04.1 LTS . On Fri, Jan 16, 2015 at 7:06 PM, Srinivasreddy R < srinivasreddy4390 at gmail.com> wrote: > hi, > Getting error while compiling dpdk on ubuntu10.04. > > > export RTE_SDK=$(pwd) > export RTE_TARGET="x86_64-ivshmem-linuxapp-gcc" > > make CONFIG_RTE_BUILD_COMBINE_LIBS=y CONFIG_RTE_BUILD_SHARED_LIB=y install > T="$RTE_TARGET" > > > == Build app/test-acl > CC main.o > LD testacl > /home/DPDK/dpdk-1.7.1/x86_64-ivshmem-linuxapp-gcc/lib/libintel_dpdk.so: > undefined reference to `log2' > /home/DPDK/dpdk-1.7.1/x86_64-ivshmem-linuxapp-gcc/lib/libintel_dpdk.so: > undefined reference to `ceil' > /home/DPDK/dpdk-1.7.1/x86_64-ivshmem-linuxapp-gcc/lib/libintel_dpdk.so: > undefined reference to `pow' > /home/DPDK/dpdk-1.7.1/x86_64-ivshmem-linuxapp-gcc/lib/libintel_dpdk.so: > undefined reference to `round' > collect2: error: ld returned 1 exit status > make[5]: *** [testacl] Error 1 > make[4]: *** [test-acl] Error 2 > make[3]: *** [app] Error 2 > make[2]: *** [all] Error 2 > make[1]: *** [x86_64-ivshmem-linuxapp-gcc_install] Error 2 > make: *** [install] Error 2 > > Following installation procedure at link : > > https://github.com/01org/dpdk-ovs/blob/development/docs/01_Installation.md#dpdk > > > thanks > srinivas. >
[dpdk-dev] [DISCUSSION] : ERROR while compiling dpdk-1.7 on ubuntu14.04
hi, Getting error while compiling dpdk on ubuntu10.04. export RTE_SDK=$(pwd) export RTE_TARGET="x86_64-ivshmem-linuxapp-gcc" make CONFIG_RTE_BUILD_COMBINE_LIBS=y CONFIG_RTE_BUILD_SHARED_LIB=y install T="$RTE_TARGET" == Build app/test-acl CC main.o LD testacl /home/DPDK/dpdk-1.7.1/x86_64-ivshmem-linuxapp-gcc/lib/libintel_dpdk.so: undefined reference to `log2' /home/DPDK/dpdk-1.7.1/x86_64-ivshmem-linuxapp-gcc/lib/libintel_dpdk.so: undefined reference to `ceil' /home/DPDK/dpdk-1.7.1/x86_64-ivshmem-linuxapp-gcc/lib/libintel_dpdk.so: undefined reference to `pow' /home/DPDK/dpdk-1.7.1/x86_64-ivshmem-linuxapp-gcc/lib/libintel_dpdk.so: undefined reference to `round' collect2: error: ld returned 1 exit status make[5]: *** [testacl] Error 1 make[4]: *** [test-acl] Error 2 make[3]: *** [app] Error 2 make[2]: *** [all] Error 2 make[1]: *** [x86_64-ivshmem-linuxapp-gcc_install] Error 2 make: *** [install] Error 2 Following installation procedure at link : https://github.com/01org/dpdk-ovs/blob/development/docs/01_Installation.md#dpdk thanks srinivas.
