Hi ，
>In addition to checking you have a compatible guest kernel version, can you >check you have iptables turned off and the 'firewalld' service stopped in the >guest. I rebuild my POC with master branch ovs and master branch qemu, but it's the same situation I think It's not mater with iptables thing. When I ping from br0 to virtual machine, I can see the vhost-user-1 port dropped tx packets. My guest os is ubuntu14.04.2, kernel is 3.16. My host os is centos7 with kernel 3.10 At 2015-08-05 00:34:16, "Loftus, Ciara" <[email protected]> wrote: >> Subject: [ovs-discuss] Vhost-User port not work and always show 'down' >> >> Hi all, >> >> I build a ovs-dpdk and vhost-user POC through INSTALL.DPDK.md. >> >> There is a br0 with dpdk0 and vhost-user-0 >> I build dpdk with 2.0.0 and ovs with branch 2.4 >> # ovs-vsctl show >> ovs-vsctl show >> c38093a7-6c7e-4d6a-a7c1-627d95acbdc6 >> Bridge "br0" >> Port "br0" >> Interface "br0" >> type: internal >> Port "vhost-user-0" >> Interface "vhost-user-0" >> type: dpdkvhostuser >> Port "dpdk0" >> Interface "dpdk0" >> type: dpdk >> >> I setup a virtual machine succesfully. qemu version is 2.3.0 which is ok for >> vhost-user >What kernel is your guest using? Anything above kernel 3.16 unfortunately does >not work. > >> >> # qemu-system-x86_64 -smp 2 -m 1024 -hda ubuntu.img -vnc :1 -chardev >> socket,id=char1,path=/usr/local/var/run/openvswitch/vhost-user-0 -netdev >> type=vhost-user,id=mynet1,chardev=char1,vhostforce -device virtio-net- >> pci,mac=22:33:44:55:66:77,netdev=mynet1 -object memory-backend- >> file,id=mem,size=1024M,mem-path=/dev/hugepages,share=on -numa >> node,memdev=mem -mem-prealloc >> qemu-system-x86_64: -netdev type=vhost- >> user,id=mynet1,chardev=char1,vhostforce: chardev "char1" went up >> >> I set the br0 10.0.0.2/24 and virtual machine eth0 10.0.0.1/24 >> But they can't ping each other >> >> # ovs-ofctl dump-flows br0 >> NXST_FLOW reply (xid=0x4): >> cookie=0x0, duration=79598.075s, table=0, n_packets=445, n_bytes=27204, >> idle_age=0, hard_age=65534, priority=0 actions=NORMAL >> >> # ovs-vsctl list interface vhost-user-0 >> _uuid : ca02a658-3f7f-4133-8b3c-cfc776154d38 >> admin_state : down >> bfd : {} >> bfd_status : {} >> cfm_fault : [] >> cfm_fault_status : [] >> cfm_flap_count : [] >> cfm_health : [] >> cfm_mpid : [] >> cfm_remote_mpids : [] >> cfm_remote_opstate : [] >> duplex : [] >> error : [] >> external_ids : {} >> ifindex : 0 >> ingress_policing_burst: 0 >> ingress_policing_rate: 0 >> lacp_current : [] >> link_resets : 1 >> link_speed : [] >> link_state : down >> lldp : {} >> mac : [] >> mac_in_use : "00:00:00:00:00:00" >> mtu : 1500 >> name : "vhost-user-0" >> ofport : 4 >> ofport_request : [] >> options : {} >> other_config : {} >> statistics : {rx_packets=0, tx_dropped=36, tx_packets=0} >> status : {} >> type : dpdkvhostuser >> >> I can see the vhost-user-0 port always show down and there are some >> dropped packets which are sent from br0. >The link state reported as "down" is ok and not an indication of an issue. > >> >> Are there some wrong with my POC? >In addition to checking you have a compatible guest kernel version, can you >check you have iptables turned off and the 'firewalld' service stopped in the >guest. > >> >> BR >> Xu Wen >> >> >
_______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
