Re: vifs not working?

[Christoph Egger <Christoph_Egger%gmx.de@localhost>]

Manuel Bouyer wrote:
> On Sun, May 25, 2008 at 03:34:02PM +0200, Christoph Egger wrote:
> > > > > > (I've been using the 2008Q1 packages, 
> > > > > > on the theory that that's the closest approximation to in sync with
> > > > > > 4.0; do newer xen packages (a) work with 4.0 and (b) fix things?)
> > > > > There's an incompatibility between the latest xentools and the 4.0 
> > > > > release kernels. So it's current or release but nothing in between :( 
> > > > > ... well reliably anyway.
> > > > On a -current dom0 kernel:
> > > >
> > > > The main problem is that xenbackendd isn't invoked at all, therefore the 
> > > > scripts never run.
> > > > xenbackendd listens for XS_WATCH_EVENT, but those never come.
> > > >
> > > > In xen/xenbus/xenbus_xs.c:process_msg  I see two type of events:
> > > > XS_READ and XS_ERROR for a block device (vbd).
> > > I'm not seeing this. xenbackendd is running fine for me
> > I re-started xenbackendd with -d and now I see, the scripts are invoked.
> > I see $xstatus have the values 1
>
> XenbusStateInitialising 
>
> > and 5.
>
> XenbusStateClosing
>
> > The scripts handle 2 and 6.
> > That makes the user look like the scripts not working.
>
> The problem here is that the device doesn't switch to state
> XenbusStateInitWait. Thsi could mean that xbdback_xenbus_create() is
> never called, or that an error occurs. In the second case there
> should be an error on dom0 console and dmesg.

xbdbackattach() is called.
xbdback_xenbus_create() is never called.

Additionally, the block script is invoked a second time for the console
and $xstatus with value 1:

xenstore-read: couldn't read path /local/domain/0/backend/console/7/0/type


Christoph