On Friday 07 August 2009, Fischer, Anna wrote: > If you do have a SRIOV NIC that supports VEPA, then I would think > that you do not have QEMU or macvtap in the setup any more though. > Simply because in that case the VM can directly access the VF on > the physical device. That would be ideal. There may be reasons why even with an SR-IOV adapter you may want to use the macvtap setup, with some extensions. E.g. guest migration becomes a lot simpler if you don't have to deal with PCI passthrough devices. If we manage to add both TX and RX zero-copy (into the guest) to the macvlan driver, we can treat an SR-IOV adapter like a VMDq adapter and get the best of both. > I do think that the macvtap driver is a good addition as a simple > and fast virtual network I/O interface, in case you do not need > full bridge functionality. It does seem to assume though that the > virtualization software uses QEMU/tap interfaces. How would this > work with a Xen para-virtualized network interface? I guess there > would need to be yet another driver? I'm not sure how Xen guest networking works, but if neither the traditional macvlan driver nor the macvtap driver are able to connect it to the external NIC, then you can probably add a third macvlan backend to handle that. Arnd <>< _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/virtualization
