* netback: Carrier off / Carrier on again, rinse, repeat
@ 2014-12-11 14:42 Christopher S. Aker
2014-12-11 14:59 ` Zoltan Kiss
0 siblings, 1 reply; 2+ messages in thread
From: Christopher S. Aker @ 2014-12-11 14:42 UTC (permalink / raw)
To: xen devel
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: netback: Carrier off / Carrier on again, rinse, repeat
2014-12-11 14:42 netback: Carrier off / Carrier on again, rinse, repeat Christopher S. Aker
@ 2014-12-11 14:59 ` Zoltan Kiss
0 siblings, 0 replies; 2+ messages in thread
From: Zoltan Kiss @ 2014-12-11 14:59 UTC (permalink / raw)
To: Christopher S. Aker, xen devel
Hi,
This has been fixed by "f48da8: xen-netback: fix unlimited guest Rx
internal queue and carrier flapping", it's already in 3.18, I don't know
if it is going to be backported to 3.17
Zoli
On 11/12/14 14:42, Christopher S. Aker wrote:
> 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@lists.xen.org
> http://lists.xen.org/xen-devel
>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2014-12-11 14:59 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-12-11 14:42 netback: Carrier off / Carrier on again, rinse, repeat Christopher S. Aker
2014-12-11 14:59 ` Zoltan Kiss
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.