From: Anthony Liguori <aliguori@us.ibm.com>
To: Randy Thelen <rthelen@netapp.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Is there example code and/or documentation for developing a Xen back-end/front-end driver pair?
Date: Mon, 26 Jun 2006 16:42:46 -0500 [thread overview]
Message-ID: <44A054D6.5050309@us.ibm.com> (raw)
In-Reply-To: <9E4997CB-BF83-4383-8F87-96E095769BB6@netapp.com>
Randy Thelen wrote:
> 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.
No. It has changed too many times (although it's probably stable enough
now to document).
In principle, once you have bring up working, making it work in Xend
isn't so bad. Do you have specific questions or are you just looking
for a where to begin?
Regards,
Anthony Liguori
> -- Randy
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2006-06-26 21:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-26 21:40 Is there example code and/or documentation for developing a Xen back-end/front-end driver pair? Randy Thelen
2006-06-26 21:42 ` Anthony Liguori [this message]
2006-06-26 22:16 ` Randy Thelen
2006-06-26 22:31 ` Ewan Mellor
2006-06-26 22:45 ` Randy Thelen
2006-06-28 13:06 ` Ewan Mellor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44A054D6.5050309@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=rthelen@netapp.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.