On 12/12/24 13:08, Ayshathul Thuhara via discuss wrote: > Hi Team, > > I am currently using OvS in our platform. I have come across OvS source in > github. I followed > https://docs.openvswitch.org/en/latest/howto/userspace-tunneling/ article to > test OvS-VXLAN. > I am able to test ping between VMs when eth0,tap0 interfaces are available. > > But when I bind the interface with vfio using dpdk and create vhost, I am > not able to ping the VMs. > I have disabled the firewalls. I have added the appctl rules as specified > in the article. Still I was not able to ping the VMs. > When I create vhost and run QEMU, I am able to get the /tmp/vm_port0 > socket. > > I used below command to execute qemu , > > /* sudo taskset -c 1-5 /usr/libexec/qemu-kvm -enable-kvm -m 4096 -smp 5 > -machine type=q35,accel=kvm -cpu host -name VM1 -no-reboot -net none -vnc > none -nographic -hda /opt/ovs/centos_os.qcow2 -netdev > type=vhost-user,id=vm_port0,chardev=vm_port0_socket -device > virtio-net-pci,netdev=vm_port0,mac=52:55:00:d1:55:01 -chardev > socket,id=vm_port0_socket,path=/tmp/vm_port0,server=on*/ > > Can you please let me know what else modification requires to ping VMs, > when dpdk is used?
See the vhost-user guide in the docuemntation: https://docs.openvswitch.org/en/latest/topics/dpdk/vhost-user/#adding-vhost-user-ports-to-the-guest-qemu Pay attention to the memory-backend configuration for QEMU. That seems to be the missing part of your command line. HTH. Best regards, Ilya Maximets. > > Sorry to contact directly, I tried to reach via OpenvSwitch official mail > (ovs-discuss-ow...@openvswitch.org). But I have not received any responses > yet. > > Best regards, > Ayshathul Thuhara _______________________________________________ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
