search for: virnetdevbridgeaddport

Displaying 4 results from an estimated 4 matches for "virnetdevbridgeaddport".

2013 Oct 16
2
libvirtError: Unable to add bridge br0 port vnet0: Operation not supported
...9;pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> and instance fails to start with: 2013-10-16 11:16:13.004+0000: 11943: info : virNetDevProbeVnetHdr:122 : Enabling IFF_VNET_HDR 2013-10-16 11:16:13.105+0000: 11943: error : virNetDevBridgeAddPort:370 : Unable to add bridge br0 port vnet0: Operation not supported If I add <virtualport type='openvswitch' /> inside <interface type='bridge'>...</interface> it seems to work fine. Is it nova-network or libvirt bug or some misconfiguration? regards -- Maciej Ga...
2015 Mar 02
2
QEMU interface type=ethernet
...o this. There is no way to have libvirt just create a tap device and leave the rest to user defined scripts. I don't think I have the necessary knowledge to add that feature in a generic way, but it seems like it would be pretty handy. I'll probably just work around it by removing the virNetDevBridgeAddPort call from our version of libvirt.
2013 Oct 16
0
Re: libvirtError: Unable to add bridge br0 port vnet0: Operation not supported
...#39;0x00' slot='0x03' > function='0x0'/> > </interface> > > and instance fails to start with: > > 2013-10-16 11:16:13.004+0000: 11943: info : virNetDevProbeVnetHdr:122 : > Enabling IFF_VNET_HDR > 2013-10-16 11:16:13.105+0000: 11943: error : virNetDevBridgeAddPort:370 : > Unable to add bridge br0 port vnet0: Operation not supported > > If I add <virtualport type='openvswitch' /> inside <interface > type='bridge'>...</interface> it seems to work fine. Is it nova-network or > libvirt bug or some misconfiguratio...
2015 Mar 02
0
Re: QEMU interface type=ethernet
...y to have libvirt just > create a tap device and leave the rest to user defined scripts. > > I don't think I have the necessary knowledge to add that feature in a > generic way, but it seems like it would be pretty handy. I'll probably > just work around it by removing the virNetDevBridgeAddPort call from > our version of libvirt. > In IRC, I was directed to this patch: https://www.redhat.com/archives/libvir-list/2015-February/msg01212.html ... which does exactly what I was looking for. It doesn't build cleanly in that state, but it's pretty trivial fix (needs actualType...