being quite a
change.
[1] - http://thread.gmane.org/gmane.comp.emulators.qemu/37714/focus=37719
-- Dragos Tatulea
Signed-off-by: Alex Williamson
Signed-off-by: Dragos Tatulea
---
diff --git a/hw/virtio-net.c b/hw/virtio-net.c
index ec1bf8d..0276f3a 100644
--- a/hw/virtio-net.c
+++ b/hw/virtio-net.c
I'd like to pick up this patch and rework it based on your
suggestions. Need it for [1]. Most opinions seem to be pointing to a
generic software mac filtering in the VLAN layer with hw support if
necessary. Here's what I had in mind:
- For the generic mac filtering we can use something similar to
V
I have created a wiki page for this [1], also added to the networking
todo list [2]. No meaty information yet. But it's enough to start
working on it.
[1] - http://www.linux-kvm.org/page/GuestProgrammableMacVlanFiltering
[2] - http://www.linux-kvm.org/page/NetworkingTodo
-- Dragos
> 1. add a secondary mac (or third, etc) address to the guest virtio-net
> interface.
Maybe I misunderstood this. Is it just setting another mac on the
guest virtio-net interface?
>
> 4. the above stuff must be controllable by host admin
> - Well, for this there are a few options:
> > admin sw
Hi,
> I'm starting a thread related to the TODO item mentioned in the
> subject. Currently still gathering info and trying to make kvm &
> macvtap play nicely together. I have used this [1] guide to set it up
> but qemu is still complaining about the PCI device address of the
> virtio-net-pci.
Hi,
I'm starting a thread related to the TODO item mentioned in the
subject. Currently still gathering info and trying to make kvm &
macvtap play nicely together. I have used this [1] guide to set it up
but qemu is still complaining about the PCI device address of the
virtio-net-pci. Tried wi
Hi,
> More importantly: anyone's going to work on this?
I'd like to work on this. Might need some assistance though.
Thanks,
Dragos
