On Thu, Jul 18, 2013 at 12:30:19AM +0800, Qiu Yu wrote: > On Thu, Jul 18, 2013 at 12:15 AM, Ben Pfaff <blp@xxxxxxxxxx> wrote: > > On Wed, Jul 17, 2013 at 6:06 AM, Qiu Yu <unicell@xxxxxxxxx> wrote: > >> After some digging in openvswitch code. My wild guess is that vlan tag > >> reconfiguring triggered iface_configure_qos (vswitchd/bridge.c), which > >> in turn called netdev_set_policing to reset ingress policing rate. > >> Although there's no ingress_policing_rate set in my case, existing > >> ingress qdisc still remove by default. > > > > The OVS database in general specifies state, not actions. That is, if > > you set no ingress_policing_rate, then OVS takes that to mean that it > > should turn off ingress policing, so it does. > > I see. So ingress policing managed outside of OVS, which is libvirt in > my case, is overridden (no ingress_policing_rate by default, means > turned off) by OVS. > > My question, however, is there any workaround, to preserve or inherit > the ingress policing managed outside of OVS after vlan tagging the > device? OVS doesn't have one now. We'd take a patch to introduce one. "VLAN tagging the device" is a bit of a misunderstanding. This behavior will take place on any change to Open vSwitch configuration. VLAN tagging is just the one example that you have encountered. _______________________________________________ libvirt-users mailing list libvirt-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvirt-users
