DPDK usage discussions
 help / color / mirror / Atom feed
From: "M R, Chengappa (Network Function Virtualization)" <cm-r@hpe.com>
To: "Rosen, Rami" <rami.rosen@intel.com>, "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] DPDK Test Suite failing with PREREQ EXCEPTION Traceback
Date: Fri, 27 Apr 2018 03:11:03 +0000	[thread overview]
Message-ID: <TU4PR8401MB065443A4D6EBC2B947A952E2998D0@TU4PR8401MB0654.NAMPRD84.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <9B0331B6EBBD0E4684FBFAEDA55776F958A0CE18@HASMSX110.ger.corp.intel.com>

Hi Rosen, 

Many thanks for acknowledging the issue addressed in the mail.

Yes I have taken care and made sure that all the required packages are installed.

However, let me go thru the link you have shared cross check the list of system requirements and get back to you.

Best Regards,
Chengappa


-----Original Message-----
From: Rosen, Rami [mailto:rami.rosen@intel.com] 
Sent: Friday, April 27, 2018 8:16 AM
To: M R, Chengappa (Network Function Virtualization) <cm-r@hpe.com>; users@dpdk.org
Subject: RE: DPDK Test Suite failing with PREREQ EXCEPTION Traceback

Hi,
The exception you got typically happens when a package is not installed on the host.

Did you install all the packages which appear in the System Requirements section of the DTS gsg ? (like python-xlwt, python-pexpect and the others) ? see:
See: http://dpdk.org/doc/dts/gsg/sys_reqs.html

In case this won't help, I would suggest to ask in the DTS mailing list, dts@dpdk.org.

Regards,
Rami Rosen

-----Original Message-----
From: users [mailto:users-bounces@dpdk.org] On Behalf Of M R, Chengappa (Network Function Virtualization)
Sent: Thursday, April 26, 2018 13:04
To: users@dpdk.org
Cc: M R, Chengappa (Network Function Virtualization) <cm-r@hpe.com>
Subject: [dpdk-users] DPDK Test Suite failing with PREREQ EXCEPTION Traceback
Importance: High

Greetings Team,

I am attempting to execute dpdk test-suite but am facing the below error PREREQ EXCEPTION Traceback

[root@tester dts]# ./dts --config-file executions/execution.cfg
                           dts:
DUT 10.70.2.6
                        tester: ssh root@10.70.2.5<mailto:root@10.70.2.5>
                        tester: ssh root@10.70.2.5<mailto:root@10.70.2.5>
                 dut.10.70.2.6: ssh root@10.70.2.6<mailto:root@10.70.2.6>
                 dut.10.70.2.6: ssh root@10.70.2.6<mailto:root@10.70.2.6>
                           dts: CACHE: Cache will not be read.
                           dts: SKIP: The DPDK setup steps will be executed.
                        tester: sed -i '/10.70.2.6/d' ~/.ssh/known_hosts
                        tester: killall scapy 2>/dev/null; echo tester
                        tester: awk '/Hugepagesize/ {print $2}' /proc/meminfo
                        tester: umount `awk '/hugetlbfs/ { print $2 }' /proc/mounts`
                        tester: awk '/hugetlbfs/ { print $2 }' /proc/mounts
                        tester: mkdir -p /mnt/huge
                        tester: mount -t hugetlbfs nodev /mnt/huge
                        tester: awk '/Hugepagesize/ {print $2}' /proc/meminfo
                        tester: echo 1024 > /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages
                        tester: scp -v dep/tgen.tgz root@10.70.2.5:~/<mailto:root@10.70.2.5:~/>
                        tester: scp -v dep/tclclient.tgz root@10.70.2.5:~/<mailto:root@10.70.2.5:~/>
                        tester: tar zxf tgen.tgz
                        tester: tar zxf tclclient.tgz
                        tester: modprobe uio
                        tester: Core0 bypassed
                        tester: modprobe igb
                        tester: modprobe ixgbe
                        tester: modprobe e1000e
                        tester: modprobe e1000
                        tester: cat /sys/bus/pci/devices/0000\:04\:00.0/vendor
                        tester: cat /sys/bus/pci/devices/0000\:04\:00.0/device
                        tester: cat /sys/bus/pci/devices/0000\:04\:00.0/vendor
                        tester: cat /sys/bus/pci/devices/0000\:04\:00.0/device
                        tester: ifconfig eno49 up
                        tester: cat /sys/bus/pci/devices/0000\:04\:00.1/vendor
                        tester: cat /sys/bus/pci/devices/0000\:04\:00.1/device
                        tester: cat /sys/bus/pci/devices/0000\:04\:00.1/vendor
                        tester: cat /sys/bus/pci/devices/0000\:04\:00.1/device
                        tester: ifconfig eno50 up
                        tester: cat /sys/bus/pci/devices/0000\:05\:00.0/vendor
                        tester: cat /sys/bus/pci/devices/0000\:05\:00.0/device
                        tester: cat /sys/bus/pci/devices/0000\:05\:00.0/vendor
                        tester: cat /sys/bus/pci/devices/0000\:05\:00.0/device
                        tester: ifconfig ens2f0 up
                        tester: cat /sys/bus/pci/devices/0000\:05\:00.1/vendor
                        tester: cat /sys/bus/pci/devices/0000\:05\:00.1/device
                        tester: cat /sys/bus/pci/devices/0000\:05\:00.1/vendor
                        tester: cat /sys/bus/pci/devices/0000\:05\:00.1/device
                        tester: ifconfig ens2f1 up
                        tester: Tester: [0000:04:00.0 10df:0720] unknow_nic
                        tester: Tester: [0000:04:00.1 10df:0720] unknow_nic
                        tester: Tester: [0000:05:00.0 8086:10fb] ens2f0
                        tester: Tester: [0000:05:00.1 8086:10fb] ens2f1
                        tester: {'intf': 'ens2f0', 'mac': '14:02:ec:74:2b:ec', 'pci': '0000:05:00.0', 'ipv4': '10.70.12.5', 'ipv6': 'fe80::1602:ecff:fe74:2bec', 'type': '8086:10fb', 'port': <net_device.NetDevice object at 0x7f7976c99790>}
                        tester: {'intf': 'ens2f1', 'mac': '14:02:ec:74:2b:ed', 'pci': '0000:05:00.1', 'ipv4': '10.70.3.5', 'ipv6': 'fe80::1602:ecff:fe74:2bed', 'type': '8086:10fb', 'port': <net_device.NetDevice object at 0x7f7976c99650>}
                           dts:  PREREQ EXCEPTION Traceback (most recent call last):
  File "/root/dts/framework/dts.py", line 341, in dts_run_prerequisties
    dutobj.prerequisites()
  File "/root/dts/framework/project_dpdk.py", line 326, in prerequisites
    self.prepare_package()
  File "/root/dts/framework/project_dpdk.py", line 273, in prepare_package
    assert (os.path.isfile(self.package) is True), "Invalid package"
AssertionError: Invalid package

                           dts: CACHE: Discarding cache.
                           dts: DTS ended



The current running configuration in our set-up is as follows:

[root@tester dts]# cat conf/ports.cfg
# DUT Port Configuration
# [DUT IP]
# ports=
#     pci=Pci BDF,intf=Kernel interface;
#     pci=Pci BDF,mac=Mac address,peer=Tester Pci BDF,numa=Port Numa
#     pci=Pci BDF,peer=IXIA:card.port
#     pci=Pci BDF,peer=Tester Pci BDF,tp_ip=$(IP),tp_path=$({PERL_PATH);
#     pci=Pci BDF,peer=Tester Pci BDF,sec_port=yes,first_port=Pci BDF;
# [VM NAME] virtual machine name; This section is for virutal scenario # ports =
#     dev_idx=device index of ports info, peer=Tester Pci BDF
[10.70.2.6]
ports =
    pci=05:00.0,intf=ens2f0;
    pci=05:00.1,intf=ens2f1;



[root@tester dts]# cat executions/execution.cfg [Execution1]
crbs=10.70.2.6
drivername=igb_uio
test_suites=hello_world
test_suites=
    cmdline,
    hello_world
targets=x86_64-native-linuxapp-gcc
parameters=nic_type=niantic:func=true



[root@tester dts]# cat conf/crbs.cfg
#DUT crbs Configuration
#[DUT IP]
#  dut_ip: DUT ip address
#  dut_user: Login DUT username
#  dut_passwd: Login DUT password
#  os: operation system type linux or freebsd #  tester_ip: Tester ip address #  tester_passwd: Tester password #  ixia_group: IXIA group name #  channels: Board channel number #  bypass_core0: Whether by pass core0 [10.70.2.6]
dut_ip=10.70.2.6
dut_user=root
dut_passwd=HP1nvent
os=fedora
tester_ip=10.70.2.5
tester_passwd=HP1nvent
channels=4


It would be helpful if anyone could guide me with the correct pointers to go over this issue and help me advance further.

Thanking in advance
Chengappa

If everyone is moving forward together, then success takes care of itself....!!

  reply	other threads:[~2018-04-27  3:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-26 10:04 M R, Chengappa (Network Function Virtualization)
2018-04-27  2:45 ` Rosen, Rami
2018-04-27  3:11   ` M R, Chengappa (Network Function Virtualization) [this message]
2018-04-27  6:04   ` M R, Chengappa (Network Function Virtualization)

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=TU4PR8401MB065443A4D6EBC2B947A952E2998D0@TU4PR8401MB0654.NAMPRD84.PROD.OUTLOOK.COM \
    --to=cm-r@hpe.com \
    --cc=rami.rosen@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).