Re: [Xen-devel] calling vif hotplug scripts more than once

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Wed, 2014-07-09 at 09:36 +0200, Olaf Hering wrote:
> On Tue, Jul 08, Ian Jackson wrote:
> 
> > Olaf Hering writes ("Re: calling vif hotplug scripts more than once"):
> > > On Tue, Jul 08, Ian Jackson wrote:
> > > > Surely the problem is just that the backend isn't going back to the
> > > > operational state.  I don't see why this would need the hotplug script
> > > > to run again.
> > > 
> > > Something needs to reconnect the device to the bridge. There is also
> > > that hotplug-status thing, which netback reads. I have to check what it
> > > does with that.
> > 
> > Why is the device removed from the bridge ?  What does that ?
> 
> Looks like netback does that, because the interface disappears.

It's an implicit behaviour of the Linux bridge, when an interface
disappears it is removed from the bridge (this isn't true of e.g.
openvswitch, so its not universal).

Now, I *thought* that the vif backend device was supposed to remain when
the frontend disconnected and would only be removed on the final
destruction of the domain (or unplug via the toolstack).

I suppose either I'm misremembering things or it has been broken at some
point. I'm CCing David and Zoltan in case what I'm remembering is
something from the XenServer kernels (since I vaguely remember this
Windows device manage thing from way back when I used to be involved in
such things).

Ian.


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