On Fri, 2015-11-06 at 11:23 +, Ian Campbell wrote:
> Please could you try 4.3~rc7-1~exp1 from experimental in dom0 and see
> if that helps?
4.3-1~exp1 was just uploaded, so you may as well try that instead.
Thanks,
Ian.
On Thu, 2015-11-05 at 19:16 +0100, Arne Klein wrote:
> 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
I've asked around upstream and it was suggested that "xen-netback:
require fewer guest Rx slots when not using GSO" wh
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
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-ckt1
On Wed, 2015-09-16 at 01:52 +0200, Arne Klein wrote:
>
[...]
> At the moment when the network in the domU completely stops working,
> there is the error message
> [2178752.854380] vif vif-33-0 vif33.0: Guest Rx stalled
> visible in dmesg in the dom0.
This will therefore be a kernel issue not a hy
Package: xen-hypervisor-4.4-amd64
Version: 4.4.1-9+deb8u1
Severity: important
A few minutes after starting a domU, network access is no longer possible from
and to it.
This does not always happen and is not easily reproducible, but seems to occur
in all newly started domUs from some point in ti
6 matches
Mail list logo
