[Pkg-xen-devel] Bug#799122: Bug#799122: xen-hypervisor-4.4-amd64: Networking of domUs stops working after a few minutes

[Ian Campbell]

Control: reassign -1 src:linux 3.16.7-ckt11-1+deb8u5
Control: found -1 4.1.3-1~bpo8+1

On Thu, 2015-11-05 at 19:16 +0100, Arne Klein wrote:
> > > We tested the current lenny kernel linux-image-3.16.0-4-amd64 as well
> > > as the backport linux-image-4.1.0-0.bpo.1-amd64 on the dom0 as well
> > > as the domU.
> > 
> > (I suppose you meant s/lenny/jessie/ ;-)
> 
> Oops, yes :)
> 
> > These are kernel ABI versions, the package release versions are things
> > like 3.16.7-ckt17-1 or 4.2.5-1~bpo8+1, which yu can either get from
> > dpkg or from /proc/version (at the end, before the date, I think).
> > 
> > If you can let me know the versions then I can more sensibly reassign
> > this to the kernel packages. It will also give some baselines to see
> > what if any fixes we do or don't have.
> 
> Thank you. The tested versions on dom0 and domU in which the problem 
> occurs are:
> 4.1.3-1~bpo8+1
> 3.16.7-ckt11-1+deb8u5

Thanks, reassigning to src:linux and letting the BTS know about these
versions.

Did you only test the matches pairs (i.e. 4.1.3 in both dom0+domU and
likewise 3.1.6.7 in both) or did you also test old and new in some
combinations? (If not then don't worry, it's probably not relevant, but
if you already have the info we may as well add it to the mix).

> I posted the problem also to the xen-user mailing list, but did not get 
> a reply there.
> 
> And I have to update one of the observations: It seems that not all 
> domUs started after the problem occurs for the first time are broken.
> After several restarts (without any changes) one of the domUs started
> working again.

I think hadn't understood this aspect of the report, are you saying
that after one domUs networking stops (with the "Guest Rx stalled" in
dom0) that some other domUs started afterwards (but per the above not
all as you first though) do not have networking from the moment they
are started? Do those new domUs also result in the stall message in
dom0?

When this happens to one domU is also there an impact on other already
running domU's or does the secondary failure only apply to new domUs?

Ian.