Xen devel - Nov 2007 - Problem adding new device & triggering backend

Hey All,

I followed the procedure in the XenIntro document to add a new device and
trigger the frontend and backend drivers over xenbus. The issue that I am
facing now is when the backend switches state, the frontend driver does NOT
pick it up. I suspect that the frontend permissions to read part of the
backend xenstore are not set properly. I did do a xenstore-chmod in the
frontend trigger script.

I then tried to create a new controller class for my device and set
permissions during domain load through the python scripts but that works for
xen-3.0.0 and not for xen-3.1. (In fact my split driver worked perfectly
with xen-3.0.) I did note the changes in the scripts/code in both versions
and made sure I appropriately handled them in my 3.1 implementation. I get
an error that says something like "backend device could not be connected:
<mydevice>" during domU create in xen-3.1.

Could anyone give me pointers on how to get around this problem? What are
the major differences in the xen python scripts in xen3.0.0 and xen3.1 for
handling devices?

Thanks for any help,

Mukil


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