[ovs-discuss] DPDK OVS with vhostuser problem

Loftus, Ciara ciara.loftus at intel.com
Mon Mar 7 11:48:15 UTC 2016


> > > Hi
> > >
> > > I followed the instructions in INSTALL.md and INSTALL.DPDK.md.
> > > I have created two ports in a bridge, and set the flows 1<->2.
> > > Doing ovs-ofctl dump-flows br0 shows it right.
> > > The purpose of this setup is to measure latency of those ports (using
> > > a simple ping).
> > >
> > > I invoke a VM, with those 2 ports. It gives those messages:
> > > 2016-03-02T17:08:17.410601Z qemu-system-x86_64: -netdev type=vhost-
> > > user,id=mynet1,chardev=char1,vhostforce: chardev "char1" went up
> 2016-
> > > 03-02T17:08:17.410851Z qemu-system-x86_64: -netdev type=vhost-
> > > user,id=mynet2,chardev=char2,vhostforce: chardev "char2" went up
> > >
> > > From within the VM (qemu), I have eth0 and eth1.
> > > I configure them as:
> > > ifconfig eth0 1.1.1.1
> > > ifconfig eth1 1.1.1.2
> > >
> > > Ping will fail though:
> > > ping 1.1.1.2 -I eth1 obviously works.
> > > ping 1.1.1.2 -I eth0 fails.
> > >
> > > In the host, I wanted to see some statistics, but ovs-ofctl dump-flows
> > > br0 fails, with this message:
> > >
> > > ovs-ofctl: /usr/local/var/run/openvswitch/br0.mgmt: failed to open
> > > socket (Connection refused)
> > >
> > > I see that this issue is right after invoking the VM.
> > >
> > > 1. What do I do wrong?
> > > 2. How can I track the packets to see why they are not forwarded
> correctly?
> >
> > Hi Eli,
> >
> > Can you give more information about your set up please - OVS / QEMU /
> > DPDK tags / commit ids?
> [Eli Britstein]
> OVS: 2.5.0
> QEMU:
> qemu-system-x86_64 --version
> QEMU emulator version 2.1.3 (qemu-2.1.3-11.fc21), Copyright (c) 2003-2008
> Fabrice Bellard
> --> Before that version I had 2.1.2. I did "yum update qemu" and got this. I
> have Fedora21, and that's the latest for this dist
> (http://rpm.pbone.net/index.php3/stat/3/srodzaj/1/search/qemu-kvm).
> I see in documentation that need QEMU 2.2, but on the other hand it was
> verified with Fedora 18/19/20.
Okay, it may be an issue with the QEMU version so.
To try another version of QEMU, you could clone the QEMU git repo (git clone git://git.qemu-project.org/qemu.git) and checkout a newer tag eg. 2.5.0
Then configure & make, and use for your vhost-user test.

Thanks,
Ciara


> DPDK: 2.2.0
> 
> > When ovs-ofctl dump-flows fails with 'connection refused', are the ovs-
> > vswitchd/ovsdb-server processes still running? Or has something crashed?
> [Eli Britstein] I didn't notice before. I see ovs-vswitchd doesn't exist in "ps"
> anymore. Probably crached.
> I did it again with --log-file and -vconsole:dbg -vsyslog:dbg -vfile:dbg.
> I see towards the end of the file "dumped all flows", but that's a try I did
> before invoking QEMU.
> Attached the log file, though I don't see any errors there...
> After invoking QEMU:
> [root at localhost openvswitch-2.5.0]# ovs-ofctl dump-flows br0
> ovs-ofctl: /usr/local/var/run/openvswitch/br0.mgmt: failed to open socket
> (Connection refused)
> 
> 
> >
> > Thanks,
> > Ciara
> >
> > >
> > > Thanks,
> > > Eli
> > >
> 
> ----------------------------------------------------------------------------------------------
> ---------------------------------------------------
> This email and any files transmitted and/or attachments with it are
> confidential and proprietary information of
> Toga Networks Ltd., and intended solely for the use of the individual or
> entity to whom they are addressed.
> If you have received this email in error please notify the system manager.
> This message contains confidential
> information of Toga Networks Ltd., and is intended only for the individual
> named. If you are not the named
> addressee you should not disseminate, distribute or copy this e-mail. Please
> notify the sender immediately
> by e-mail if you have received this e-mail by mistake and delete this e-mail
> from your system. If you are not
> the intended recipient you are notified that disclosing, copying, distributing
> or taking any action in reliance on
> the contents of this information is strictly prohibited.
> ----------------------------------------------------------------------------------------------
> --------------------------------------------------




More information about the discuss mailing list