Re: [Xen-devel] about probing xenbus drivers again

[Mark Williamson <mark.williamson@xxxxxxxxxxxx>]

> When i start xend in dom0 nothing happens. Then i use xm create to create
> domain 1. Probe functions of vbd and vif drivers are executed but probe
> function of my driver isn't. Then i try to create some nodes (name of my
> driver is prmigr):
>
> xenstore-write /local/domain/0/device/prmigr hi
> xenstore-write /local/domain/0/device/prmigr/hello hi
>
> And i see that frontend's probe function is invoked.
> The same happens with 1-st domain. But when i try:

Makes sense: for VBDs and VIFs, Xend creates the xenstore nodes that cause the 
probe functions to be called.  See 
xen-unstable.hg/tools/python/xen/xend/server/{netif,blkif,DevController}.py 
for where this happens in the current codebase...

>
> xenstore-write /local/domain/0/backend/prmigr hi
> xenstore-write /local/domain/0/backend/prmigr/hello hi
>
> Nothing happens.

Can't think of a good reason for this off the top of my head - somebody else 
may be able to comment.

Cheers,
Mark

> So, please, explain me
> 1) why there are nodes vbd and vif in devices and backend directories but
> there isn't prmigr node? vbd and vif driver invoke xenbus_register_driver
> or xenbus_register_backend like my driver does. How to make xen to create
> prmigr node while initialization?
> 2)why writing to the backend/prmigr node doesn't affect to the xen and
> appropriate probe function isn't executed?
>
> Thanks a lot.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel