WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Is there example code and/or documentation for developing a

To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Is there example code and/or documentation for developing a Xen back-end/front-end driver pair?
From: Randy Thelen <rthelen@xxxxxxxxxx>
Date: Mon, 26 Jun 2006 14:40:27 -0700
Delivery-date: Mon, 26 Jun 2006 14:40:56 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Folks --

I'm walking through all the Xen Python code and driver code to determine how to build a custom back-end/front-end driver pair. I'm not using any of the existing transport types (blkif, netif, etc.). So, I need to start from scratch supporting configuration file elements in Xen down to the drivers in the kernel.

If there are any good pointers as to how to build something new from the ground up within the framework of the existing Xen Daemon and be- fe pairing, I'd really like to read it.

-- Randy

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