Re: [Xen-users] domU loses network after a while

[Olivier Hanesse <olivier.hanesse@xxxxxxxxx>]

Hello,

About the netback driver, in Debian Kernel, I can see those  :

  * xen: Fix crash in netback.

  * Update Xen patch.
     - Fix checksum offloading in netback.

Olivier

2010/11/19 Pasi Kärkkäinen <pasik@xxxxxx>

On Fri, Nov 19, 2010 at 10:27:05AM +0100, Olivier Hanesse wrote:
>    Hello Pasi,
>
>    Are you thinking about the smartpoll patch ?
>
>  * [x86/xen] Disable netfront's smartpoll mode by default.
>
>    If so, yes the debian kernel we are using, is fine about this issue.
>

Yep, that.

Also there was another bug in the dom0 kernel netback driver,
but I think that should be fixed if the smartpoll bug is fixed..

unless only the other patch was pulled to Debian kernel..

-- Pasi

>    Regards
>
>    Olivier
>
>    2010/11/19 Pasi Kärkkäinen <[1]pasik@xxxxxx>

>
>      On Thu, Nov 18, 2010 at 10:35:46PM +0100, Erwan RENIER wrote:
>      >    Le 18/11/2010 19:33, Stein van Oevelen a écrit :
>      >
>      >        Nathan Friess wrote:
>      >
>      >          Hi,
>      >
>      >          I have a host running Debian Squeeze with Xen 4.0.1 installed
>      from
>      >          the Debian repository.  My host is working fine running 10
>      domUs,
>      >          except that after some number of days one or more domUs lose
>      their
>      >          network interface.  In dom0 and domU I'm running kernel
>      >          2.6.32-5-xen-amd64 (PV kernel in Debian repo), and interfaces
>      are in
>      >          a bridged config.
>      >
>      >        In case anyone runs into something similar, I did figure out
>      how to
>      >        resolve my issue without having to reboot the domU... which is
>      a
>      >        slight improvement I suppose.
>      >
>      >        Running
>      >           xm network-detach domUName 0
>      >
>      >        Causes eth0 to disappear in the domain, and the following to
>      show up
>      >        in dmesg:
>      >
>      >          net eth0: xennet_release_rx_bufs: fix me for copying
>      receiver.
>      >
>      >        Then running an xm network-attach will bring eth0 back and
>      everything
>      >        will be okay.
>      >
>      >        I also tried rmmoding xen_netfront in domU before I figured out
>      the
>      >        network-detach, but this doesn't help.  When modprobing again,
>      the
>      >        domU says "eth0: link is not ready".  This also causes any
>      subsequent
>      >        attempt to network-detach in dom0 to get stuck and eventually
>      timeout
>      >        with "Device 0 (vif) could not be disconnected."
>      >
>      >        Also, when the vif is stuck, the TX dropped packets shown in
>      dom0 is
>      >        steadily increasing.  It seems that dom0 is having trouble
>      sending
>      >        packets to domU because one of the two gets stuck in an
>      unexpected
>      >        state.  At least doing a network-detach will reset the state
>      and allow
>      >        things to run properly again.
>      >
>      >        Nathan
>      >
>      >        _______________________________________________
>      >        Xen-users mailing list

>      >        [1][2]Xen-users@xxxxxxxxxxxxxxxxxxx
>      >        [2][3]http://lists.xensource.com/xen-users

>      >
>      >      I have a similar issue, however my DomU's seem to get their
>      connection
>      >      back after a while automatically, most of the time it happens
>      when I
>      >      physically login to the Dom0 :/
>      >
>      >
>
>      Are you guys running the latest kernel?
>
>      This sounds like a bug that was fixed two months ago (or so)
>      in the upstream "xen/stable-2.6.32.x" git branch..
>
>      -- Pasi
>
>      _______________________________________________
>      Xen-users mailing list

>      [4]Xen-users@xxxxxxxxxxxxxxxxxxx
>      [5]http://lists.xensource.com/xen-users
>
> References
>
>    Visible links
>    1. mailto:pasik@xxxxxx
>    2. mailto:Xen-users@xxxxxxxxxxxxxxxxxxx
>    3. http://lists.xensource.com/xen-users
>    4. mailto:Xen-users@xxxxxxxxxxxxxxxxxxx
>    5. http://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users