On Thursday 10 December 2009 19:14:28 Alexander Graf wrote: > > This is something I also have been thinking about, but it is not what > > I was referring to above. I think it would be good to keep the three > > cases (macvlan, VMDq, SR-IOV) as similar as possible from the user > > perspective, so using macvlan as an infrastructure for all of them > > sounds reasonable to me. > > Oh, so you'd basically do -net vt-d,if=eth0 and the rest would > automatically work? That's a pretty slick idea! I was only referring to how they get set up under the covers, e.g. creating the virtual device, configuring the MAC address etc, not the qemu side, but that would probably make sense as well. Or even better, qemu should probably not even know the difference between macvlan and VT-d. In both cases, it would open a macvtap file, but for VT-d adapters, the macvlan infrastructure can use hardware support, much in the way that VLAN tagging gets offloaded automatically to the hardware. Arnd <>< _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/virtualization
