On Tue, 2011-08-16 at 10:51 +0200, Andreas Pflug wrote:
Sorry I forgot about this issue for such a long time.
I wonder if this issue is fixed by this commit upstream:
commit d0e5d83284dac15c015bb48115b6780f5a6413cd
Author: David Vrabel <[email protected]>
Date: Fri Sep 30 06:37:51 2011 +0000
net: xen-netback: correctly restart Tx after a VM restore/migrate
If a VM is saved and restored (or migrated) the netback driver will
no
longer process any Tx packets from the frontend. xenvif_up() does
not
schedule the processing of any pending Tx requests from the front
end
because the carrier is off. Without this initial kick the frontend
just adds Tx requests to the ring without raising an event (until
the
ring is full).
This was caused by 47103041e91794acdbc6165da0ae288d844c820b (net:
xen-netback: convert to hw_features) which reordered the calls to
xenvif_up() and netif_carrier_on() in xenvif_connect().
Signed-off-by: David Vrabel <[email protected]>
That commit made it into v3.1-rc9 and v3.0.9 so should be in the current
Wheezy/Sid kernels.
Thanks,
Ian.
--
Ian Campbell
Current Noise: Ufomammut - Blind
If you wish to succeed, consult three old people.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
