Vrouter agent crash happens because agent is running in debug mode, which results in assertion on vrouter operation errors you can remove “debug = 1” from “DEFAULT” section from contrail-vrouter-agent.conf file and restart contrail-vrouter-agent, to avoid this crash
Regarding second point “FlowKey Mismatch”, vrouter-agent has a mechanism to recover from these errors, so it should not impact any functionality. however I will check if I can find reason for this error to happen. -- Prabhjot From: Dev <[email protected]> on behalf of "Rhine, Jay (Nokia - US)" <[email protected]> Date: Friday, 17 June 2016 at 23:51 To: Rajagopalan Sivaramakrishnan <[email protected]> Cc: "[email protected]" <[email protected]>, "[email protected]" <[email protected]> Subject: Re: [opencontrail-dev] Help with configure contrail-vrouter-dpdk on a Compute Raja, OpenContrail Team, Thank you for all the help you have provided for getting a basic Contrail DPDK vrouter up and running! However, now that it is running I’m noticing a stability issue that I’m hoping you can help with. Specifically, I have noticed that when I add a new DPDK VM sometimes the new VM and other VM’s on the same compute node stop being able to pass packets. It seems like often the packets are able to pass for a few seconds before the VM stops working. I just had this happen again. The VM came up and received a DHCP address. I even saw a few pings successful before the new VM and the rest of the VM’s on the compute stopped working. Looking in logs I see the following: 1) In the contrail-vrouter-dpdk-stdout.log file, I see “2016-06-17 12:12:36,427 DPCORE: vrouter soft reset start”. According to the log, this happened 8 seconds after the interface for the new VM (tapfd389e2a-59) had been successfully added to the vrouter. 2) In contrail-vrouter-agent.log, I see “VRouter operation failed. Error <14:Flow Key Mismatch with same gen id>. Object <Flow : 364112 with Source IP: 192.168.2.7 Source port: 52890 Destination IP: 192.168.2.2 Destination port: 53 Protocol 17>. Operation <Change>. Message number :1611” . 3) The contrail-vrouter-agent restarted. 4) In contrail-vrouter-agent-stdout.log, I see “controller/src/ksync/ksync_object.cc:545: virtual void KSyncEntry::ErrorHandler(int, uint32_t, KSyncEntry::KSyncEvent) const: Assertion `err == 0' failed.” There is no timestamp in the contrail-vrouter-agent-stdout.log, but I believe this is connected. I have include the relevant section of all these logs below. Do you have any suggestions on how to prevent this issue from occurring? Is there a known problem with the vrouter that causes soft reset? I am currently using a vrouter built from the master trunk. When something like this does occur is there a good recovery procedure? I know that if I hard reboot each VM on the compute node it will normally recover. However, is there a better way to fix the networking on the compute node? Thanks a lot! Jay See below for detailed logs: contrail-vrouter-agent-stdout.log: contrail-vrouter-agent: controller/src/ksync/ksync_object.cc:545: virtual void KSyncEntry::ErrorHandler(int, uint32_t, KSyncEntry::KSyncEvent) const: Assertion `err == 0' failed. Config file </etc/contrail/contrail-vrouter-agent.conf> parsing completed. log4cplus:ERROR No appenders could be found for logger (SANDESH). log4cplus:ERROR Please initialize the log4cplus system properly. in TAsioServerClient constructor in start contrail-vrouter-agent.log: 2016-06-17 Fri 12:12:34:179.419 EDT HP-RBC-11 [Thread 140104335668992, Pid 58676]: Flow event = FlowHandleAssign flow = 0x7f6c80636ba0 flow->flow_handle = 4294967295 flow->gen_id = 0 ksync = 0x7f6c800263a0 Ksync->hash_id = 4294967295 Ksync->gen_id = 0 new_flow_handle = 273252 new_gen_id = 2 2016-06-17 Fri 12:12:34:179.446 EDT HP-RBC-11 [Thread 140104335668992, Pid 58676]: Flow event = FlowUpdate flow = 0x7f6c806366e0 flow->flow_handle = 364112 flow->gen_id = 1 ksync = 0x7f6c80026470 Ksync->hash_id = 364112 Ksync->gen_id = 1 new_flow_handle = 364112 new_gen_id = 1 2016-06-17 Fri 12:12:34:218.370 EDT HP-RBC-11 [Thread 140103777253120, Pid 58676]: VRouter operation failed. Error <14:Flow Key Mismatch with same gen id>. Object <Flow : 364112 with Source IP: 192.168.2.7 Source port: 52890 Destination IP: 192.168.2.2 Destination port: 53 Protocol 17>. Operation <Change>. Message number :1611 2016-06-17 Fri 12:12:34:218.383 EDT HP-RBC-11 [Thread 140104335668992, Pid 58676]: VRouter [SYS_DEBUG]: VRouterError: VRouter operation failed. Error < 14 : Flow Key Mismatch with same gen id >. Object < Flow : 364112 with Source IP: 192.168.2.7 Source port: 52890 Destination IP: 192.168.2.2 Destination port: 53 Protocol 17 >. Operation < Change >. Message number : 1611 controller/src/ksync/ksync_object.cc 537 2016-06-17 Fri 12:12:35:332.255 EDT HP-RBC-11 [Thread 139660972152768, Pid 47595]: vhost interface name : vhost0 2016-06-17 Fri 12:12:35:332.357 EDT HP-RBC-11 [Thread 139660972152768, Pid 47595]: vhost IP Address : 172.16.63.60/24 2016-06-17 Fri 12:12:35:332.371 EDT HP-RBC-11 [Thread 139660972152768, Pid 47595]: vhost gateway : 172.16.63.1 2016-06-17 Fri 12:12:35:332.382 EDT HP-RBC-11 [Thread 139660972152768, Pid 47595]: Ethernet port : p2p2 2016-06-17 Fri 12:12:35:332.393 EDT HP-RBC-11 [Thread 139660972152768, Pid 47595]: XMPP Server-1 : 0.0.0.0 2016-06-17 Fri 12:12:35:332.404 EDT HP-RBC-11 [Thread 139660972152768, Pid 47595]: XMPP Server-2 : 0.0.0.0 2016-06-17 Fri 12:12:35:332.415 EDT HP-RBC-11 [Thread 139660972152768, Pid 47595]: Xmpp Authentication : 0 2016-06-17 Fri 12:12:35:332.427 EDT HP-RBC-11 [Thread 139660972152768, Pid 47595]: DNS Server-1 : 0.0.0.0 2016-06-17 Fri 12:12:35:332.438 EDT HP-RBC-11 [Thread 139660972152768, Pid 47595]: DNS Port-1 : 53 contrail-vrouter-dpdk-stdout.log: 2016-06-17 12:12:26,706 VROUTER: Adding vif 7 (gen. 9) virtual device tapfd389e2a-59 2016-06-17 12:12:26,706 VROUTER: lcore 11 TX to HW queue 0 2016-06-17 12:12:26,706 VROUTER: lcore 12 TX to HW queue 1 2016-06-17 12:12:26,706 VROUTER: lcore 13 TX to HW queue 2 2016-06-17 12:12:26,706 VROUTER: lcore 8 TX to HW queue 3 2016-06-17 12:12:26,706 VROUTER: lcore 9 TX to HW queue 4 2016-06-17 12:12:26,706 VROUTER: lcore 10 TX to HW queue 5 2016-06-17 12:12:26,706 VROUTER: lcore 11 RX from HW queue 0 2016-06-17 12:12:26,706 UVHOST: Adding vif 7 virtual device tapfd389e2a-59 2016-06-17 12:12:26,706 UVHOST: vif 7 socket tapfd389e2a-59 FD is 69 2016-06-17 12:12:27,184 UVHOST: Handling client connection FD 69 2016-06-17 12:12:27,184 UVHOST: FD 69 accepted new client connection FD 71 2016-06-17 12:12:27,292 UVHOST: Client tapfd389e2a-59: no handler defined for message 3 2016-06-17 12:12:27,292 UVHOST: Client tapfd389e2a-59: handling message 1 2016-06-17 12:12:27,292 UVHOST: GET FEATURES: returns 0x4020003 2016-06-17 12:12:27,292 UVHOST: Client tapfd389e2a-59: handling message 13 2016-06-17 12:12:27,292 UVHOST: SET VRING CALL: vring 0 FD 72 2016-06-17 12:12:27,292 UVHOST: Client tapfd389e2a-59: handling message 13 2016-06-17 12:12:27,292 UVHOST: SET VRING CALL: vring 1 FD 73 2016-06-17 12:12:28,815 UVHOST: Client tapfd389e2a-59: handling message 13 2016-06-17 12:12:28,815 UVHOST: SET VRING CALL: vring 0 FD 74 2016-06-17 12:12:28,815 UVHOST: Client tapfd389e2a-59: handling message 13 2016-06-17 12:12:28,815 UVHOST: SET VRING CALL: vring 1 FD 72 2016-06-17 12:12:28,815 UVHOST: Client tapfd389e2a-59: handling message 2 2016-06-17 12:12:28,815 UVHOST: SET FEATURES: 0x20003 2016-06-17 12:12:28,815 UVHOST: Client tapfd389e2a-59: handling message 5 2016-06-17 12:12:28,815 UVHOST: SET MEM TABLE: 2016-06-17 12:12:28,815 UVHOST: Client tapfd389e2a-59: unmapping 0 memory regions: 2016-06-17 12:12:28,815 UVHOST: Client tapfd389e2a-59: mapping 2 memory regions: 2016-06-17 12:12:28,815 UVHOST: 0: FD 73 addr 0x0 size 0xa0000 off 0x0 2016-06-17 12:12:28,815 UVHOST: 1: FD 75 addr 0xc0000 size 0x1ff40000 off 0xc0000 2016-06-17 12:12:28,815 UVHOST: Client tapfd389e2a-59: handling message 8 2016-06-17 12:12:28,815 UVHOST: SET VRING NUM: vring 0 num 256 2016-06-17 12:12:28,815 UVHOST: Client tapfd389e2a-59: handling message 10 2016-06-17 12:12:28,815 UVHOST: SET VRING BASE: vring 0 base 0 2016-06-17 12:12:28,815 UVHOST: Client tapfd389e2a-59: handling message 9 2016-06-17 12:12:28,815 UVHOST: SET VRING ADDR: vring 0 flags 0x0 desc 0x7f13fb8b8000 used 0x7f13fb8ba000 avail 0x7f13fb8b9000 2016-06-17 12:12:28,815 UVHOST: Client tapfd389e2a-59: vring 0 is ready 2016-06-17 12:12:28,815 UVHOST: Client tapfd389e2a-59: no handler defined for message 12 2016-06-17 12:12:28,815 UVHOST: Client tapfd389e2a-59: handling message 8 2016-06-17 12:12:28,815 UVHOST: SET VRING NUM: vring 1 num 256 2016-06-17 12:12:28,815 UVHOST: Client tapfd389e2a-59: handling message 10 2016-06-17 12:12:28,815 UVHOST: SET VRING BASE: vring 1 base 0 2016-06-17 12:12:28,815 UVHOST: Client tapfd389e2a-59: handling message 9 2016-06-17 12:12:28,815 UVHOST: SET VRING ADDR: vring 1 flags 0x0 desc 0x7f13fb8bc000 used 0x7f13fb8be000 avail 0x7f13fb8bd000 2016-06-17 12:12:28,815 UVHOST: Client tapfd389e2a-59: vring 1 is ready 2016-06-17 12:12:28,815 UVHOST: Client tapfd389e2a-59: no handler defined for message 12 2016-06-17 12:12:36,427 DPCORE: vrouter soft reset start 2016-06-17 12:12:36,427 VROUTER: Deleting vif 0 eth device 2016-06-17 12:12:36,427 VROUTER: releasing lcore 8 TX queue 2016-06-17 12:12:36,427 VROUTER: releasing lcore 9 TX queue 2016-06-17 12:12:36,427 VROUTER: releasing lcore 10 RX queue 2016-06-17 12:12:36,427 VROUTER: releasing lcore 10 TX queue 2016-06-17 12:12:36,427 VROUTER: releasing lcore 11 RX queue 2016-06-17 12:12:36,427 VROUTER: releasing lcore 11 TX queue 2016-06-17 12:12:36,427 VROUTER: releasing lcore 12 RX queue 2016-06-17 12:12:36,427 VROUTER: releasing lcore 12 TX queue 2016-06-17 12:12:36,427 VROUTER: releasing lcore 13 RX queue 2016-06-17 12:12:36,427 VROUTER: releasing lcore 13 TX queue 2016-06-17 12:12:36,482 VROUTER: Deleting vif 1 KNI device 2016-06-17 12:12:36,482 VROUTER: releasing lcore 8 TX queue 2016-06-17 12:12:36,482 VROUTER: releasing lcore 9 TX queue 2016-06-17 12:12:36,482 VROUTER: releasing lcore 10 RX queue 2016-06-17 12:12:36,482 VROUTER: releasing lcore 10 TX queue 2016-06-17 12:12:36,482 VROUTER: releasing lcore 11 TX queue 2016-06-17 12:12:36,482 VROUTER: releasing lcore 12 TX queue 2016-06-17 12:12:36,482 VROUTER: releasing lcore 13 TX queue 2016-06-17 12:12:39,522 VROUTER: Deleting vif 2 packet device 2016-06-17 12:12:39,522 VROUTER: Deleting vif 3 virtual device 2016-06-17 12:12:39,522 VROUTER: releasing lcore 8 TX queue 2016-06-17 12:12:39,522 VROUTER: releasing lcore 9 TX queue 2016-06-17 12:12:39,522 VROUTER: releasing lcore 10 TX queue 2016-06-17 12:12:39,522 VROUTER: releasing lcore 11 RX queue 2016-06-17 12:12:39,522 VROUTER: releasing lcore 11 TX queue 2016-06-17 12:12:39,522 VROUTER: releasing lcore 12 TX queue 2016-06-17 12:12:39,522 VROUTER: releasing lcore 13 TX queue 2016-06-17 12:12:39,522 VROUTER: Deleting vif 4 virtual device 2016-06-17 12:12:39,522 UVHOST: Deleting vif 3 virtual device 2016-06-17 12:12:39,522 UVHOST: Client tap5d087a8e-76: unmapping 2 memory regions: 2016-06-17 12:12:39,522 UVHOST: 0: unmapping addr 0x0 size 0xa0000 2016-06-17 12:12:39,522 UVHOST: 1: unmapping addr 0xc0000 size 0x1ff40000 2016-06-17 12:12:39,523 VROUTER: releasing lcore 8 TX queue 2016-06-17 12:12:39,523 VROUTER: releasing lcore 9 TX queue 2016-06-17 12:12:39,523 VROUTER: releasing lcore 10 TX queue 2016-06-17 12:12:39,523 VROUTER: releasing lcore 11 TX queue 2016-06-17 12:12:39,523 VROUTER: releasing lcore 12 RX queue 2016-06-17 12:12:39,523 VROUTER: releasing lcore 12 TX queue 2016-06-17 12:12:39,523 VROUTER: releasing lcore 13 TX queue 2016-06-17 12:12:39,523 VROUTER: Deleting vif 5 virtual device 2016-06-17 12:12:39,523 UVHOST: Deleting vif 4 virtual device 2016-06-17 12:12:39,523 UVHOST: Client tapaba78102-07: unmapping 2 memory regions: 2016-06-17 12:12:39,523 UVHOST: 0: unmapping addr 0x0 size 0xa0000 2016-06-17 12:12:39,523 UVHOST: 1: unmapping addr 0xc0000 size 0x1ff40000 2016-06-17 12:12:39,523 VROUTER: releasing lcore 8 TX queue 2016-06-17 12:12:39,523 VROUTER: releasing lcore 9 TX queue 2016-06-17 12:12:39,523 VROUTER: releasing lcore 10 TX queue 2016-06-17 12:12:39,523 VROUTER: releasing lcore 11 TX queue 2016-06-17 12:12:39,523 VROUTER: releasing lcore 12 TX queue 2016-06-17 12:12:39,523 VROUTER: releasing lcore 13 RX queue 2016-06-17 12:12:39,523 VROUTER: releasing lcore 13 TX queue 2016-06-17 12:12:39,523 VROUTER: Deleting vif 6 virtual device 2016-06-17 12:12:39,523 UVHOST: Deleting vif 5 virtual device 2016-06-17 12:12:39,523 UVHOST: Client tap13af2624-60: unmapping 2 memory regions: 2016-06-17 12:12:39,523 UVHOST: 0: unmapping addr 0x0 size 0xa0000 2016-06-17 12:12:39,523 UVHOST: 1: unmapping addr 0xc0000 size 0x1ff40000 2016-06-17 12:12:39,523 VROUTER: releasing lcore 8 TX queue 2016-06-17 12:12:39,523 VROUTER: releasing lcore 9 TX queue 2016-06-17 12:12:39,523 VROUTER: releasing lcore 10 RX queue 2016-06-17 12:12:39,523 VROUTER: releasing lcore 10 TX queue 2016-06-17 12:12:39,523 VROUTER: releasing lcore 11 TX queue 2016-06-17 12:12:39,523 VROUTER: releasing lcore 12 TX queue 2016-06-17 12:12:39,523 VROUTER: releasing lcore 13 TX queue 2016-06-17 12:12:39,523 VROUTER: Deleting vif 7 virtual device 2016-06-17 12:12:39,523 UVHOST: Deleting vif 6 virtual device 2016-06-17 12:12:39,523 UVHOST: Client tapa79cfef0-2d: unmapping 2 memory regions: 2016-06-17 12:12:39,523 UVHOST: 0: unmapping addr 0x0 size 0xa0000 2016-06-17 12:12:39,523 UVHOST: 1: unmapping addr 0xc0000 size 0x1ff40000 2016-06-17 12:12:39,524 VROUTER: releasing lcore 8 TX queue 2016-06-17 12:12:39,524 VROUTER: releasing lcore 9 TX queue 2016-06-17 12:12:39,524 VROUTER: releasing lcore 10 TX queue 2016-06-17 12:12:39,524 VROUTER: releasing lcore 11 RX queue 2016-06-17 12:12:39,524 VROUTER: releasing lcore 11 TX queue 2016-06-17 12:12:39,524 VROUTER: releasing lcore 12 TX queue 2016-06-17 12:12:39,524 VROUTER: releasing lcore 13 TX queue 2016-06-17 12:12:39,524 UVHOST: Deleting vif 7 virtual device 2016-06-17 12:12:39,524 UVHOST: Client tapfd389e2a-59: unmapping 2 memory regions: 2016-06-17 12:12:39,524 UVHOST: 0: unmapping addr 0x0 size 0xa0000 2016-06-17 12:12:39,524 UVHOST: 1: unmapping addr 0xc0000 size 0x1ff40000 2016-06-17 12:12:39,550 DPCORE: vrouter soft reset done (0) 2016-06-17 12:12:39,565 VROUTER: Adding vif 0 (gen. 10) eth device 0 PCI 0000:07:00.1 MAC 8c:dc:d4:aa:6c:65 (vif MAC 8c:dc:d4:aa:6c:65) 2016-06-17 12:12:39,565 VROUTER: setup 4 RSS queue(s) and 0 filtering queue(s) 2016-06-17 12:12:39,731 VROUTER: lcore 10 TX to HW queue 0 2016-06-17 12:12:39,731 VROUTER: lcore 11 TX to HW queue 1 2016-06-17 12:12:39,731 VROUTER: lcore 12 TX to HW queue 2 2016-06-17 12:12:39,731 VROUTER: lcore 13 TX to HW queue 3 2016-06-17 12:12:39,731 VROUTER: lcore 8 TX to HW queue 4 2016-06-17 12:12:39,731 VROUTER: lcore 9 TX to HW queue 5 2016-06-17 12:12:39,731 VROUTER: lcore 10 RX from HW queue 0 2016-06-17 12:12:39,731 VROUTER: lcore 11 RX from HW queue 1 2016-06-17 12:12:39,731 VROUTER: lcore 12 RX from HW queue 2 2016-06-17 12:12:39,731 VROUTER: lcore 13 RX from HW queue 3 2016-06-17 12:12:39,731 VROUTER: Adding vif 1 (gen. 11) KNI device vhost0 at eth device 0 MAC 8c:dc:d4:aa:6c:65 (vif MAC 8c:dc:d4:aa:6c:65) 2016-06-17 12:12:39,731 VROUTER: bind KNI kernel thread to CPU 4 2016-06-17 12:12:39,731 KNI: pci: 07:00:01 8086:10fb 2016-06-17 12:12:39,771 VROUTER: lcore 10 TX to HW queue 0 2016-06-17 12:12:39,771 VROUTER: lcore 11 TX to SW ring 2016-06-17 12:12:39,771 VROUTER: lcore 10 now has 1 ring(s) to push 2016-06-17 12:12:39,771 VROUTER: lcore 12 TX to SW ring 2016-06-17 12:12:39,771 VROUTER: lcore 10 now has 2 ring(s) to push 2016-06-17 12:12:39,771 VROUTER: lcore 13 TX to SW ring 2016-06-17 12:12:39,771 VROUTER: lcore 10 now has 3 ring(s) to push 2016-06-17 12:12:39,771 VROUTER: lcore 8 TX to SW ring 2016-06-17 12:12:39,771 VROUTER: lcore 10 now has 4 ring(s) to push 2016-06-17 12:12:39,771 VROUTER: lcore 9 TX to SW ring 2016-06-17 12:12:39,771 VROUTER: lcore 10 now has 5 ring(s) to push 2016-06-17 12:12:39,771 VROUTER: lcore 10 RX from HW queue 0 2016-06-17 12:12:39,772 VROUTER: Adding vif 2 (gen. 12) packet device unix 2016-06-17 12:12:39,772 USOCK: usock_alloc[7f8fba9fb700]: new socket FD 52 2016-06-17 12:12:39,772 USOCK: usock_alloc[7f8fba9fb700]: setting socket FD 52 send buff size. Buffer size set to 18320000 (requested 9216000) 2016-06-17 12:12:41,489 VROUTER: Adding vif 3 (gen. 13) virtual device tap5d087a8e-76 2016-06-17 12:12:41,489 VROUTER: lcore 11 TX to HW queue 0 2016-06-17 12:12:41,489 VROUTER: lcore 12 TX to HW queue 1 2016-06-17 12:12:41,489 VROUTER: lcore 13 TX to HW queue 2 2016-06-17 12:12:41,489 VROUTER: lcore 8 TX to HW queue 3 2016-06-17 12:12:41,489 VROUTER: lcore 9 TX to HW queue 4 2016-06-17 12:12:41,489 VROUTER: lcore 10 TX to HW queue 5 2016-06-17 12:12:41,489 VROUTER: lcore 11 RX from HW queue 0 2016-06-17 12:12:41,489 UVHOST: Adding vif 3 virtual device tap5d087a8e-76 2016-06-17 12:12:41,489 UVHOST: vif 3 socket tap5d087a8e-76 FD is 53 2016-06-17 12:12:41,489 VROUTER: Adding vif 4 (gen. 14) virtual device tapfd389e2a-59 2016-06-17 12:12:41,489 VROUTER: lcore 12 TX to HW queue 0 2016-06-17 12:12:41,489 VROUTER: lcore 13 TX to HW queue 1 2016-06-17 12:12:41,489 VROUTER: lcore 8 TX to HW queue 2 2016-06-17 12:12:41,489 VROUTER: lcore 9 TX to HW queue 3 2016-06-17 12:12:41,489 VROUTER: lcore 10 TX to HW queue 4 2016-06-17 12:12:41,489 VROUTER: lcore 11 TX to HW queue 5 2016-06-17 12:12:41,489 VROUTER: lcore 12 RX from HW queue 0 2016-06-17 12:12:41,489 UVHOST: Adding vif 4 virtual device tapfd389e2a-59 2016-06-17 12:12:41,489 UVHOST: vif 4 socket tapfd389e2a-59 FD is 56 2016-06-17 12:12:41,490 VROUTER: Adding vif 5 (gen. 15) virtual device tapaba78102-07 2016-06-17 12:12:41,490 VROUTER: lcore 13 TX to HW queue 0 2016-06-17 12:12:41,490 VROUTER: lcore 8 TX to HW queue 1 2016-06-17 12:12:41,490 VROUTER: lcore 9 TX to HW queue 2 2016-06-17 12:12:41,490 VROUTER: lcore 10 TX to HW queue 3 2016-06-17 12:12:41,490 VROUTER: lcore 11 TX to HW queue 4 2016-06-17 12:12:41,490 VROUTER: lcore 12 TX to HW queue 5 2016-06-17 12:12:41,490 VROUTER: lcore 13 RX from HW queue 0 2016-06-17 12:12:41,490 UVHOST: Adding vif 5 virtual device tapaba78102-07 2016-06-17 12:12:41,490 UVHOST: vif 5 socket tapaba78102-07 FD is 57 2016-06-17 12:12:41,490 VROUTER: Adding vif 6 (gen. 16) virtual device tap13af2624-60 2016-06-17 12:12:41,490 VROUTER: lcore 10 TX to HW queue 0 2016-06-17 12:12:41,490 VROUTER: lcore 11 TX to HW queue 1 2016-06-17 12:12:41,490 VROUTER: lcore 12 TX to HW queue 2 2016-06-17 12:12:41,490 VROUTER: lcore 13 TX to HW queue 3 2016-06-17 12:12:41,490 VROUTER: lcore 8 TX to HW queue 4 2016-06-17 12:12:41,490 VROUTER: lcore 9 TX to HW queue 5 2016-06-17 12:12:41,490 VROUTER: lcore 10 RX from HW queue 0 2016-06-17 12:12:41,490 UVHOST: Adding vif 6 virtual device tap13af2624-60 2016-06-17 12:12:41,490 UVHOST: vif 6 socket tap13af2624-60 FD is 58 2016-06-17 12:12:41,490 VROUTER: Adding vif 7 (gen. 17) virtual device tapa79cfef0-2d 2016-06-17 12:12:41,490 VROUTER: lcore 11 TX to HW queue 0 2016-06-17 12:12:41,490 VROUTER: lcore 12 TX to HW queue 1 2016-06-17 12:12:41,490 VROUTER: lcore 13 TX to HW queue 2 2016-06-17 12:12:41,490 VROUTER: lcore 8 TX to HW queue 3 2016-06-17 12:12:41,490 VROUTER: lcore 9 TX to HW queue 4 2016-06-17 12:12:41,490 VROUTER: lcore 10 TX to HW queue 5 2016-06-17 12:12:41,490 VROUTER: lcore 11 RX from HW queue 0 2016-06-17 12:12:41,490 UVHOST: Adding vif 7 virtual device tapa79cfef0-2d 2016-06-17 12:12:41,490 UVHOST: vif 7 socket tapa79cfef0-2d FD is 59 2016-06-17 12:12:49,862 VROUTER: Configuring eth device 0 UP 2016-06-17 12:15:56,994 VROUTER: Adding monitoring vif 4351 (gen. 18) KNI device mon0 to monitor vif 0 2016-06-17 12:15:56,994 VROUTER: bind KNI kernel thread to CPU 4 2016-06-17 12:15:56,994 KNI: pci: 07:00:01 8086:10fb 2016-06-17 12:15:57,036 VROUTER: lcore 12 TX to HW queue 0 2016-06-17 12:15:57,036 VROUTER: lcore 13 TX to SW ring 2016-06-17 12:15:57,036 VROUTER: lcore 12 now has 1 ring(s) to push 2016-06-17 12:15:57,036 VROUTER: lcore 8 TX to SW ring 2016-06-17 12:15:57,036 VROUTER: lcore 12 now has 2 ring(s) to push 2016-06-17 12:15:57,036 VROUTER: lcore 9 TX to SW ring 2016-06-17 12:15:57,036 VROUTER: lcore 12 now has 3 ring(s) to push 2016-06-17 12:15:57,036 VROUTER: lcore 10 TX to SW ring 2016-06-17 12:15:57,036 VROUTER: lcore 12 now has 4 ring(s) to push 2016-06-17 12:15:57,036 VROUTER: lcore 11 TX to SW ring 2016-06-17 12:15:57,036 VROUTER: lcore 12 now has 5 ring(s) to push 2016-06-17 12:15:57,052 VROUTER: Configuring eth device 0 UP 2016-06-17 12:16:01,341 VROUTER: Deleting monitoring vif 4351 KNI device to monitor vif 0 2016-06-17 12:16:01,341 VROUTER: releasing lcore 8 TX queue 2016-06-17 12:16:01,341 VROUTER: releasing lcore 9 TX queue 2016-06-17 12:16:01,341 VROUTER: releasing lcore 10 TX queue 2016-06-17 12:16:01,341 VROUTER: releasing lcore 11 TX queue 2016-06-17 12:16:01,341 VROUTER: releasing lcore 12 TX queue 2016-06-17 12:16:01,341 VROUTER: releasing lcore 13 TX queue 2016-06-17 12:16:57,647 VROUTER: Adding monitoring vif 4346 (gen. 19) KNI device mon5 to monitor vif 5 2016-06-17 12:16:57,647 VROUTER: bind KNI kernel thread to CPU 4 2016-06-17 12:16:57,647 KNI: pci: 07:00:01 8086:10fb 2016-06-17 12:16:57,688 VROUTER: lcore 12 TX to HW queue 0 2016-06-17 12:16:57,688 VROUTER: lcore 13 TX to SW ring 2016-06-17 12:16:57,688 VROUTER: lcore 12 now has 1 ring(s) to push 2016-06-17 12:16:57,688 VROUTER: lcore 8 TX to SW ring 2016-06-17 12:16:57,688 VROUTER: lcore 12 now has 2 ring(s) to push 2016-06-17 12:16:57,688 VROUTER: lcore 9 TX to SW ring 2016-06-17 12:16:57,688 VROUTER: lcore 12 now has 3 ring(s) to push 2016-06-17 12:16:57,688 VROUTER: lcore 10 TX to SW ring 2016-06-17 12:16:57,688 VROUTER: lcore 12 now has 4 ring(s) to push 2016-06-17 12:16:57,688 VROUTER: lcore 11 TX to SW ring 2016-06-17 12:16:57,688 VROUTER: lcore 12 now has 5 ring(s) to push 2016-06-17 12:16:57,706 VROUTER: Configuring eth device 0 UP 2016-06-17 12:17:07,965 VROUTER: Deleting monitoring vif 4346 KNI device to monitor vif 5 2016-06-17 12:17:07,965 VROUTER: releasing lcore 8 TX queue 2016-06-17 12:17:07,965 VROUTER: releasing lcore 9 TX queue 2016-06-17 12:17:07,965 VROUTER: releasing lcore 10 TX queue 2016-06-17 12:17:07,965 VROUTER: releasing lcore 11 TX queue 2016-06-17 12:17:07,965 VROUTER: releasing lcore 12 TX queue 2016-06-17 12:17:07,965 VROUTER: releasing lcore 13 TX queue ---- Jay Rhine, CISSP
_______________________________________________ Dev mailing list [email protected] http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org
