On 02/26/2015 04:18 PM, Loftus, Ciara wrote:
On 02/24/2015 05:13 PM, Loftus, Ciara wrote:
Hi Marcel,
On 02/23/2015 12:57 PM, Marcel Apfelbaum wrote:
Hi,
I CC-ed the developers that submitted the patch.
Thanks again,
Marcel
Hi,
Thank you for responding to my mail!
You're welcome.
Regarding patch: [ovs-dev] [PATCH RFC v6 1/1] netdev-dpdk: add dpdk
vhost ports
http://openvswitch.org/pipermail/dev/2015-January/050279.html
What are the Qemu versions supported?(At least the ones that were
tested)
(V5 of this patch was tested with QEMU versions 1.4.2 and 1.6.2)
This patch was tested with QEMU 1.6.2 and later 2.1.0.
Thanks, I tried with QEMU 1.6.2 with no luck.
The reason I ask is that I tried it with a Fedora 21 host with both
QEMU 2.1.2 and QEMU 1.6.2 and I had no luck connecting the guest to
the switch.
With QEMU 1.6.2 please make sure that you have hugepages set up and
that you provide the
"-mem-path /path/to/hugepages -mem-prealloc"
arguments on the QEMU command line.
Used that (I read all the documentation - a pretty good one, thanks!)
Secondly, please make sure that the name of the vhost port you
provided
to add-port matches the "ifname" parameter on the QEMU command line:
OVS: ovs-vsctl add-port br0 ovsdpdk0 -- set Interface type=dpdkvhost
QEMU: -netdev
type=tap,id=net1,script=no,downscript=no,ifname=ovsdpdk0,vhost=on
I had this one too.
Thirdly, ensure that the eventfd_link.ko module is inserted.
Checked.
The ovsdpdk0 port always remains DOWN.
Any pointers will be greatly appreciated.
Have you tested with traffic? Or are you relying on the config/state
UP/DOWN to verify if the port is connected to the switch?
I did both, used ofctl show <bridge> and tried to ping between
guest<->host and guest<->other host. No luck.
A little description of my setup:
I have:
- a regular Fedora 21 host with a regular NIC connected back-to-back to:
- a host with Fedora 21 and
- Intel DPDK-enabled NIC
- DPDK 1.8.0
- Openvswitch (latest) patched with this patch and the other 2
recommended patches.
- I set br0 ip address to something like 192.168.0.100 and I am able
to ping between
br0 and the other regular host. Both the guest and the other host
have ips configured.
However, I am not able to ping between br0<->guest or regular host<-
guest.
Hi,
Marcel, please ensure that the firewalld service is disabled on the VM.
I will, thank you.
Secondly, please ensure that you have configured routing such that pings to the
guest go through the bridge, rather than the default route.
Excuse my lack of OVS knowledge, but how do I do that? I add a specific flow
rule like ovs-ofctl add-flow ... ?
Thanks again for the involvement,
Marcel
[...]
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
