Bug#767261: [Pkg-xen-devel] Bug#767261: xen-hypervisor-4.4-amd64: host lockup when DomU network iface is down
On Sat, 2014-11-08 at 15:13 -0500, Gedalya wrote:
> On 11/08/2014 08:44 AM, Gedalya wrote:
> >>>>
> >>> Tried to just frankenport xen-netback from 3.18 into 3.16, didn't work
> >>> very well ;-)
> >> Did you backport just the above or the full set of changes from 3.18?
> > I tried to "simplify" (avoid having to edit code myself..) by just
> > copying the full xen-netback from 3.18 as it is.
> > I did have to revert "c835a6 net: set name_assign_type in
> > alloc_netdev()" to get it to compile, but then it gave me a kernel bug
> > as soon as a xen guest booted up.
> > (see attached if it matters)
> > I'll try to apply just those 3 patches and see how it goes.
>
> Important: I have no idea what I'm doing!!
:-D
>
> So I cherry-picked the following
> xen-netback: reintroduce guest Rx stall detection
> xen-netback: fix unlimited guest Rx internal queue and carrier flapping
> xen-netback: make feature-rx-notify mandatory
> xen-netback: Don't deschedule NAPI when carrier off
> xen-netback: Fix vif->disable handling
> xen-netback: Turn off the carrier if the guest is not able to receive
> xen-netback: Using a new state bit instead of carrier
>
> I'm attaching the two commits for which I had to manually resolve
> conflicts, and finally a debian quilt patch including all 7 commits for
> 3.16.7-2
>
> So far this is working, behavior is as I described for 3.18.
>
> Perhaps this could be helpful but someone should certainly review it.
Thanks, I actually ended up backporting a few more patches, effectively
all of the netback changes since v3.16 since they all looked like useful
fixes, and it reduced the conflicts.
If you were able to test the kernel from
http://xenbits.xen.org/people/ianc/debian/767261/ that would be great
(I'm struggling a bit to regroove my usual test box with something
useful).
Ian.
Reply to: