finally, I have found that it is ovs bug.
when reboot vm, libvirt will call ovs-vsctl del-port,
this cmd will cause other port's tc ingress rule automatically remove.
http://openvswitch.org/pipermail/discuss/2015-July/018318.html
I have reported a bug for ovs, and they have admitted it.
anyway
On 20.07.2015 10:43, ychen wrote:
> hi:
> when I use openstack devstack to test QOS, wired phenomenon appeared,
> I set qos ingress rule in tapB, but when I reboot tapA, the ingress rule of
> tapB automatically removed, but the egress rule is still exist.
> Test enviroment:
> Linux: ubuntu 14.04.
hi:
when I use openstack devstack to test QOS, wired phenomenon appeared,
I set qos ingress rule in tapB, but when I reboot tapA, the ingress rule of
tapB automatically removed, but the egress rule is still exist.
Test enviroment:
Linux: ubuntu 14.04.1 LTS
kernel: 3.13.0-32-generic
libvirt: 1.2.2
