hi, Team

I am using “server mode” image to deploy VPP in my VIRL environment. The
particular image work well in VIRL 1.2 environment, I can start VPP service
and config i/f and IP for VPP. But When I snapshot the image , download to
local and then upload to other VIRL 1.3 server ( also I tried VIRL 1.5
server), this image seem can’t work well. I can still boot this image but
when I tried to enable VPP service, encountering the following error:



******* error message in VIRL 1.3 *******************



cisco@vpp-1:~$ systemctl status vpp.service

‚óè vpp.service - vector packet processing engine

   Loaded: loaded (/lib/systemd/system/vpp.service; enabled; vendor preset:
enabled)

   Active: inactive (dead) (Result: exit-code) since Wed 2018-02-14
05:32:29 UTC; 1min 13s ago

  Process: 1360 ExecStopPost=/bin/rm -f /dev/shm/db /dev/shm/global_vm
/dev/shm/vpe-api (code=exited, status=0/SUCCESS)

  Process: 1357 ExecStart=/usr/bin/vpp -c /etc/vpp/startup.conf
(code=exited, status=1/FAILURE)

  Process: 1353 ExecStartPre=/sbin/modprobe uio_pci_generic (code=exited,
status=1/FAILURE)

  Process: 1350 ExecStartPre=/bin/rm -f /dev/shm/db /dev/shm/global_vm
/dev/shm/vpe-api (code=exited, status=0/SUCCESS)

 Main PID: 1357 (code=exited, status=1/FAILURE)

cisco@vpp-1:~$

cisco@vpp-1:~$

cisco@vpp-1:~$



********** as comparison, this image has used to work in VIRL 1.2
*****************





cisco@vpp-1:~$ sudo systemctl status vpp.service

[sudo] password for cisco:

‚óè vpp.service - vector packet processing engine

   Loaded: loaded (/lib/systemd/system/vpp.service; enabled; vendor preset:
enabled)

   Active: active (running) since Wed 2018-02-14 00:09:32 UTC; 5h 25min ago

  Process: 1119 ExecStartPre=/sbin/modprobe uio_pci_generic (code=exited,
status=1/FAILURE)

  Process: 1075 ExecStartPre=/bin/rm -f /dev/shm/db /dev/shm/global_vm
/dev/shm/vpe-api (code=exited, status=0/SUCCESS)

 Main PID: 1135 (vpp_main)

    Tasks: 3

   Memory: 81.8M

      CPU: 5h 24min 52.306s

   CGroup: /system.slice/vpp.service

           └─1135 /usr/bin/vpp -c /etc/vpp/startup.conf



Feb 14 00:09:33 vpp-1 /usr/bin/vpp[1135]: load_one_plugin:63: Loaded
plugin: /usr/lib/vpp_api_test_plugins/ioam_trace_test_plugin.so

Feb 14 00:09:33 vpp-1 vpp[1135]: /usr/bin/vpp[1135]: vlib_pci_bind_to_uio:
Skipping PCI device 0000:00:03.0 as host interface ens3 is up

Feb 14 00:09:33 vpp-1 /usr/bin/vpp[1135]: vlib_pci_bind_to_uio: Skipping
PCI device 0000:00:03.0 as host interface ens3 is up

Feb 14 00:09:33 vpp-1 vpp[1135]: /usr/bin/vpp[1135]: dpdk_config:1215: EAL
init args: -c 1 -n 4 --huge-dir /run/vpp/hugepages --file-prefix vpp -b
0000:00:03.0 --master-lcore 0 --socket-mem 256

Feb 14 00:09:33 vpp-1 /usr/bin/vpp[1135]: dpdk_config:1215: EAL init args:
-c 1 -n 4 --huge-dir /run/vpp/hugepages --file-prefix vpp -b 0000:00:03.0
--master-lcore 0 --socket-mem 256

Feb 14 00:09:34 vpp-1 vpp[1135]: EAL: WARNING: cpu flags constant_tsc=yes
nonstop_tsc=no -> using unreliable clock cycles !

Feb 14 00:09:34 vpp-1 vnet[1135]: EAL: WARNING: cpu flags constant_tsc=yes
nonstop_tsc=no -> using unreliable clock cycles !

Feb 14 00:09:34 vpp-1 vpp[1135]: EAL:   Invalid NUMA socket, default to 0

Feb 14 00:09:34 vpp-1 vnet[1135]: EAL:   Invalid NUMA socket, default to 0

Feb 14 00:09:34 vpp-1 vnet[1135]: dpdk_ipsec_process:271: not enough
Cryptodevs, default to OpenSSL IPsec

cisco@vpp-1:~$

cisco@vpp-1:~$

Reply via email to