Your message dated Tue, 13 Dec 2022 22:17:33 +0100
with message-id <Y5jr7djlwfqFkiQ/@eldamar.lan>
and subject line Re: Bug#1026035: xen netback broken with 5.10.0-20-amd64 in
s-p-u
has caused the Debian Bug report #1026035,
regarding xen netback broken with 5.10.0-20-amd64 in s-p-u
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1026035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026035
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Version: 5.10.158-1
Dear maintainers,
we just upgraded our xen test cluster's kernel to the latest kernel from
s-p-u and noticed that network communication is broken. We do have a
'classic' setup with bridges in dom0. After upgrading dom0's kernel, no
communication is possible for the domU.
We can see packets arrive at the domU and packets leave the domU; but they
never arrive at the virtual interface in dom0 (rx counter stays at 0 and error
counters stay at 0 too).
When migrating the domU back to the other server which has not been
upgraded, the machine is reachable again.
If there is anything we can do to help fixing that issue, we'll gladly do
that!
Thank you very much!
-- Adi
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 5.10.158-2
Hi Adi,
On Tue, Dec 13, 2022 at 03:40:04PM +0100, Adi Kriegisch wrote:
> Source: linux
> Version: 5.10.158-1
>
> Dear maintainers,
>
> we just upgraded our xen test cluster's kernel to the latest kernel from
> s-p-u and noticed that network communication is broken. We do have a
> 'classic' setup with bridges in dom0. After upgrading dom0's kernel, no
> communication is possible for the domU.
>
> We can see packets arrive at the domU and packets leave the domU; but they
> never arrive at the virtual interface in dom0 (rx counter stays at 0 and error
> counters stay at 0 too).
>
> When migrating the domU back to the other server which has not been
> upgraded, the machine is reachable again.
>
> If there is anything we can do to help fixing that issue, we'll gladly do
> that!
>
> Thank you very much!
This is adressed with a subsequent upload which should hit the archive
soon and hopefully in time for the point release (I did miss to close
this bug with the upload, doing so manually to have proper version
tracking).
Regards,
Salvatore
--- End Message ---
