[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [MirageOS-devel] Xen VIF configuration for tap devices
On 30 October 2014 13:42, Richard Mortier <Richard.Mortier@xxxxxxxxxxxxxxxx> wrote: all; I think Masoud found that the problem was in Netif naming. In the earlier version of the mirage-net library, the Manager would provide direct access to the device names and there was higher programmability in netif programmability. I think Masoud got this right. Â
As I mentioned to Masoud, I basically used oflops together with the pktgen kernel module for high throughput traffic generation. Two critical points to get things working is to make separate bridges for each vif pair in the Dom0 and also, if you are planning to work with iperf and real applications, you must disable tx offloading on the non-unikernel VMs. I remember I had a problem to get TCP connections across a mirage switch because I was getting bad checksums on the receiver side.  more generally-- is http://wiki.xenproject.org/wiki/Xen_Networking the canonical location for info on how to configure and manage networking on xen vms? I think ovs doesn't do anything special for Xen vifs in comparison to traditional ethernet linux devices. The only debugging I usually do is to check through the `ovs-vsctl show` Âif vif are assigned to the appropriate bridges. Â
Charalampos Rotsos
PhD student The University of Cambridge Computer Laboratory William Gates Building JJ Thomson Avenue Cambridge CB3 0FD Phone: +44-(0) 1223 767032 Email: cr409@xxxxxxxxxxxx _______________________________________________ MirageOS-devel mailing list MirageOS-devel@xxxxxxxxxxxxxxxxxxxx http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |