[Xen-devel] netback: Carrier off / Carrier on again, rinse, repeat

["Christopher S. Aker" <caker@xxxxxxxxxxxx>]

Xen: 4.4.2-pre (28573:f6f6236af933) + xsa111, xsa112, xsa114
Dom0: 3.17.4

We recently moved our dom0 from 3.10.x to 3.17.4, in order to avoid a netback 
host crash that has been plaguing us.  After doing so, the new multi-queue 
netback stuff constantly on/offs carrier on the vif, spamming the console, and 
making the bridge device leave forwarding state and then immediately reenter 
forwarding state.

vif vif-43-0 vif43.0: Carrier off due to lack of guest response on queue 0
br0: port 44(vif43.0) entered disabled state
vif vif-43-0 vif43.0: Carrier on again
br0: port 44(vif43.0) entered forwarding state
br0: port 44(vif43.0) entered forwarding state
br0: port 44(vif43.0) entered forwarding state
vif vif-43-0 vif43.0: Carrier off due to lack of guest response on queue 0
br0: port 44(vif43.0) entered disabled state
vif vif-43-0 vif43.0: Carrier on again
br0: port 44(vif43.0) entered forwarding state
br0: port 44(vif43.0) entered forwarding state
br0: port 44(vif43.0) entered forwarding state
vif vif-113-0 vif113.0: Carrier off due to lack of guest response on queue 0
br0: port 108(vif113.0) entered disabled state
vif vif-113-0 vif113.0: Carrier on again
br0: port 108(vif113.0) entered forwarding state
br0: port 108(vif113.0) entered forwarding state
br0: port 108(vif113.0) entered forwarding state
vif vif-43-0 vif43.0: Carrier off due to lack of guest response on queue 0
br0: port 44(vif43.0) entered disabled state
vif vif-43-0 vif43.0: Carrier on again
br0: port 44(vif43.0) entered forwarding state
br0: port 44(vif43.0) entered forwarding state
br0: port 44(vif43.0) entered forwarding state
vif vif-43-0 vif43.0: Carrier off due to lack of guest response on queue 0
br0: port 44(vif43.0) entered disabled state
vif vif-43-0 vif43.0: Carrier on again
br0: port 44(vif43.0) entered forwarding state
br0: port 44(vif43.0) entered forwarding state
br0: port 44(vif43.0) entered forwarding state

(This is in the span of a few minutes, however it is non-stop)

If this is normal expected operation then obviously we can live with the 
console messages, but - I just wanted to report this in the case it is not 
expected behavior.

Thanks,
-Chris


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel