On Fri, Apr 21, 2017 at 06:04:34PM +0000, Damjan Marion (damarion) wrote: > > On 21 Apr 2017, at 20:02, Ernst, Eric <eric.er...@intel.com> wrote: > > > > Ugh. Definitely not. I was just trying to run following the directions I > > could find after installing VPP binary package. > > > > What needs to change from the default? > > Then you likely need to install vpp-plugins package... >
Thanks Damjan. I installed the vpp-plugins package and can use multiple worker threads without crashing. Since I'll only be using DPDK, I shouldn't hit that crash again, but seems like a bug/issue anyway. --Eric > > > > Thanks, > > Eric > > > > -----Original Message----- > > From: Damjan Marion (damarion) [mailto:damar...@cisco.com] > > Sent: Friday, April 21, 2017 10:59 AM > > To: Ernst, Eric <eric.er...@intel.com> > > Cc: Steven Luong (sluong) <slu...@cisco.com>; Billy McFall > > <bmcf...@redhat.com>; vpp-dev@lists.fd.io > > Subject: Re: [vpp-dev] Connectivity issue when using vhost-user on 17.04? > > > >> > >> On 21 Apr 2017, at 18:28, Ernst, Eric <eric.er...@intel.com> wrote: > >> > >> Backtrace and startup.conf found below: > >> > >> ===>Backtrace:: > >> (gdb) run -c /etc/vpp/startup.conf > >> Starting program: /usr/bin/vpp -c /etc/vpp/startup.conf [Thread > >> debugging using libthread_db enabled] Using host libthread_db library > >> "/lib/x86_64-linux-gnu/libthread_db.so.1". > >> vlib_plugin_early_init:360: plugin path /usr/lib/vpp_plugins [New > >> Thread 0x7fff97041700 (LWP 68889)] [New Thread 0x7fff96840700 (LWP > >> 68890)] [New Thread 0x7fff9603f700 (LWP 68891)] > >> /usr/bin/vpp[68885]: unknown input ` > >> unix_physmem_init: use huge pages > >> unix_physmem_init: use huge pages > >> > >> Thread 2 "vpp_wk_0" received signal SIGSEGV, Segmentation fault. > >> [Switching to Thread 0x7fff97041700 (LWP 68889)] > >> 0x00007ffff7149a62 in ?? () from > >> /usr/lib/x86_64-linux-gnu/libvnet.so.0 > >> (gdb) bt > >> #0 0x00007ffff7149a62 in ?? () from > >> /usr/lib/x86_64-linux-gnu/libvnet.so.0 > >> #1 0x00007ffff7757f89 in dispatch_node () from > >> /usr/lib/x86_64-linux-gnu/libvlib.so.0 > >> #2 0x00007ffff775827d in dispatch_pending_node () from > >> /usr/lib/x86_64-linux-gnu/libvlib.so.0 > >> #3 0x00007ffff7758537 in vlib_worker_loop () from > >> /usr/lib/x86_64-linux-gnu/libvlib.so.0 > >> #4 0x00007ffff69e9c60 in clib_calljmp () from > >> /usr/lib/x86_64-linux-gnu/libvppinfra.so.0 > >> #5 0x00007fff97040f20 in ?? () > >> #6 0x00007ffff67a96ca in start_thread (arg=0x0) at > >> pthread_create.c:333 > >> #7 0x0000000000000000 in ?? () > >> > >> --- > >> > >> ===>Startup.conf: > >> vhost-user { > >> coalesce-frames 0 > >> } > >> > >> unix { > >> nodaemon > >> log /tmp/vpp.log > >> full-coredump > >> } > >> > >> api-trace { > >> on > >> } > >> > >> api-segment { > >> gid vpp > >> } > >> > >> cpu { > >> skip-cores 4 > >> workers 2 > >> } > >> > > > > You are trying to run VPP without dpdk plugin loaded. Is this intentional? > > > > > > _______________________________________________ > > vpp-dev mailing list > > vpp-dev@lists.fd.io > > https://lists.fd.io/mailman/listinfo/vpp-dev > _______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
