Re: vifs not working?

[Manuel Bouyer <bouyer%antioche.eu.org@localhost>]

On Sun, May 25, 2008 at 05:15:12PM +0200, Christoph Egger wrote:
> Manuel Bouyer wrote:
> >On Sun, May 25, 2008 at 04:43:51PM +0200, Christoph Egger wrote:
> >>>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.
> >
> >It's supposed to be called from xenbus. I don't know why it's not called
> >in your case; is it with xen 3.1.4 or 3.2.1 ?
> 
> on both.
> 
> >>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
> >
> >that's expected, but it should be harmless.
> 
> why is this expected? what is the connection of a console to a vbd ?

In the sense that I'm used to see it since Xen 3.1.0. I don't know why
xenbackendd calls the vbd_script for the console (I though the message
was comming from xenbackendd itself, but it seems it's not). But it doesn't
prevent things from working.

-- 
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
     NetBSD: 26 ans d'experience feront toujours la difference
--