> > Thanks Ciara for your kindly highlights! > > After tailing the logs and basic troubleshooting, we finally can have 2 VMs to > ping to each other. One dpdkvhostuser interface is for each VM and we have > to new add flows based on dpdkvhostuser ofport numbers. Another issue is > that we run pktgen-dpdk 2.9.1 inside of VM but no packets counted from > pktgen terminal display. It is so weird that we only see 128 tx packets > bursted > out and then nothing is continue working. After that, we try to dump-flows > via ovs-ofctl utility but it shows "connection refued". I am not sure have any > one of you guys ideas here? Thanks!!!
I'm inexperienced with pktgen so I haven't seen this problem before myself. When you receive the "connection refused" error from OVS are both the ovsdb-server and ovs-vswitchd processes still running or has anything crashed at this point? If there has been a crash can you please post the gdb trace of the ovs-vswitchd process. Thanks. Ciara > > Bridge "ovsbr0" > Port "ovsbr0" > Interface "ovsbr0" > type: internal > Port "dpdk1" > Interface "dpdk1" > type: dpdk > Port "dpdk0" > Interface "dpdk0" > type: dpdk > Port "vhost-user1" > Interface "vhost-user1" > type: dpdkvhostuser > Port "vhost-user0" > Interface "vhost-user0" > type: dpdkvhostuser > > -----Original Message----- > From: Loftus, Ciara [mailto:ciara.lof...@intel.com] > Sent: Monday, September 21, 2015 5:23 PM > To: Star.Chang > Cc: 'discuss@openvswitch.org' > Subject: RE: [ovs-discuss] vhost-user state in openvswitch > > > > > We bring 2 VMs up with vhost-user type. We can see eth0 interfaces > > created in 2 VMs with proper mac address we assign. After IP address > > assignment, 2 VMs could not PING to each other when they are in the > > same network segment. > > However, we check link up state via ovs-ofctl utility but LINK_DOWN as > > below. > > Have any one with experiences and give some helps ... Thanks!!! > > $ sudo ./utilities/ovs-ofctl show ovsbr0 OFPT_FEATURES_REPLY > > (xid=0x2): dpid:00000670da615e4a n_tables:254, n_buffers:256 > > capabilities: FLOW_STATS TABLE_STATS PORT_STATS QUEUE_STATS > > ARP_MATCH_IP > > actions: output enqueue set_vlan_vid set_vlan_pcp strip_vlan > > mod_dl_src mod_dl_dst mod_nw_src mod_nw_dst mod_nw_tos > mod_tp_src > > mod_tp_dst > > 1(vhost-user1): addr:00:00:00:00:00:00 > > config: PORT_DOWN > > state: LINK_DOWN > > speed: 0 Mbps now, 0 Mbps max > > 2(vhost-user2): addr:00:00:00:00:00:00 > > config: PORT_DOWN > > state: LINK_DOWN > > speed: 0 Mbps now, 0 Mbps max > > LOCAL(ovsbr0): addr:06:70:da:61:5e:4a > > config: PORT_DOWN > > state: LINK_DOWN > > current: 10MB-FD COPPER > > speed: 10 Mbps now, 0 Mbps max > > OFPT_GET_CONFIG_REPLY (xid=0x4): frags=normal miss_send_len=0 > > Hi, > > You can ignore the LINK_DOWN state - it does not give the correct state of > the port at the moment. > > Can you make sure the default (NORMAL) flow is installed in the switch > which should allow these pings to be sent/received? eg: > ovs-ofctl dump-flows br0 > NXST_FLOW reply (xid=0x4): > cookie=0x0, duration=136.745s, table=0, n_packets=121, n_bytes=22148, > idle_age=15, priority=0 actions=NORMAL > > Also some quick things to check: > - Make sure you are using a separate vhost-user port per VM ie. not using > the same socket device on 2 VMs. > - You are using QEMU v2.2.0 or later > > Thanks, > Ciara _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss