[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Problem adding new device & triggering backend


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: "Mukil Kesavan" <mukilk@xxxxxxxxx>
  • Date: Tue, 20 Nov 2007 14:50:37 -0500
  • Delivery-date: Tue, 20 Nov 2007 11:51:16 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=ujss7lcr6I0MV2ihvSF0yXYMcCpwbg4coWWA2W0j7l8AlMVxpvOY3FGCXSyUM1AIsJcqL2QUH91bskYAWesFicgh+LAGValaU/D/Uf9dcuX8hUVf0po0MfChG22BOThgPcOzfAnObRqjvwBpJOMVbN3ALSsMrchGhtvHaN4pwNY=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.