[Xen-devel] Mismatch between dom0 netback and domU netfront?

[Chas Williams III <ciwillia@xxxxxxxxxxx>]

For various reasons, I need to unload and load a new netfront from a
relatively modern distro (say Fedora 21) while running under RHEL5's
dom0.  On rmmod of the netfront in domU, the netback in dom0 seems to go
immediately to Closed and skips going through Closing.  So the netback
fails to release its grants and when I attempt to load a new netfront
in domU, it additionally hangs waiting to talk to the netback because
the netback never comes out of Closed.

Rebooting the domU clears up the issue of course until I attempt to
rmmod/insmod the netfront again.

I can't upgrade the dom0 because it is someone else's cloud
infrastructure.

My current workaround is to force my state to Closing during .remove()
and force my state to Initialising during .probe().  This seems to
convince the netback in dom0 to do the right thing.

dom0 from more modern distributions don't seem to have this issue.

Was there a previous method to signal the netback in dom0 that the
netfront was going away?

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel