[libvirt] [PATCH v2] qemu: handle multicast overflow on macvtap NIC_RX_FILTER_CHANGED

2018-11-30 Thread Jason Baron
in this state. When 'overflow' is set in the guest, let's turn this into ALLMULTI on the host. Signed-off-by: Jason Baron --- v1->v2: 1. check for < 0 in virNetDevSetRcvAllMulti() (Michal Privoznik) 2. restrict overflow check to VIR_NETDEV_RX_FILTER_MODE_NORMAL mode as to

Re: [libvirt] [PATCH] qemu: handle multicast overflow on macvtap for NIC_RX_FILTER_CHANGED

2018-11-26 Thread Jason Baron
On 11/26/18 11:24 AM, Michal Privoznik wrote: > On 11/26/18 5:10 PM, Michal Privoznik wrote: >> On 11/21/18 4:04 PM, Jason Baron wrote: >>> Guest network devices can set 'overflow' when there are a number of >>> multicast >>> ips configured. For

[libvirt] [PATCH] qemu: handle multicast overflow on macvtap for NIC_RX_FILTER_CHANGED

2018-11-21 Thread Jason Baron
in this state. When 'overflow' is set in the guest, let's turn this into ALLMULTI on the host. Signed-off-by: Jason Baron --- src/qemu/qemu_driver.c | 26 +++--- 1 file changed, 19 insertions(+), 7 deletions(-) diff --git a/src/qemu/qemu_driver.c b/src/qemu/q

Re: [libvirt] opening tap devices that are created in a container

2018-07-11 Thread Jason Baron
On 07/11/2018 06:10 AM, nert@wheatley wrote: > On Mon, Jul 09, 2018 at 05:00:49PM -0400, Jason Baron wrote: >> >> >> On 07/08/2018 02:01 AM, Martin Kletzander wrote: >>> On Thu, Jul 05, 2018 at 06:24:20PM +0200, Roman Mohr wrote: >>>> On Thu,

Re: [libvirt] opening tap devices that are created in a container

2018-07-09 Thread Jason Baron
On 07/08/2018 02:01 AM, Martin Kletzander wrote: > On Thu, Jul 05, 2018 at 06:24:20PM +0200, Roman Mohr wrote: >> On Thu, Jul 5, 2018 at 4:20 PM Jason Baron wrote: >> >>> Hi, >>> >>> Opening tap devices, such as macvtap, that are created in container

Re: [libvirt] opening tap devices that are created in a container

2018-07-09 Thread Jason Baron
On 07/05/2018 12:10 PM, Daniel P. Berrangé wrote: > On Thu, Jul 05, 2018 at 10:20:16AM -0400, Jason Baron wrote: >> Hi, >> >> Opening tap devices, such as macvtap, that are created in containers is >> problematic because the interface for opening tap devices is via &g

[libvirt] opening tap devices that are created in a container

2018-07-05 Thread Jason Baron
Hi, Opening tap devices, such as macvtap, that are created in containers is problematic because the interface for opening tap devices is via /dev/tapNN and devtmpfs is not typically mounted inside a container as its not namespace aware. It is possible to do a mknod() in the container, once the tap