From: Wei Liu <liuw@liuw.name>
To: Daniel Castro <evil.dani@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Block front and back connection
Date: Tue, 9 Aug 2011 10:27:55 +0800 [thread overview]
Message-ID: <20110809022755.GA1783@limbo> (raw)
In-Reply-To: <CAP2B85_YZFqLWSqOMJv9wg1_3L7aHMgdrdAfeKbrqb0HHuiYOw@mail.gmail.com>
On Mon, Aug 08, 2011 at 11:17:52PM +0900, Daniel Castro wrote:
> Hello,
>
> I am trying to make my frontend block driver connect to xen block
> backend. I have the ring and gref, yet I do not know where in xenstore
> should I write the keys to tell the backend to connect to my frontend.
>
You can find some clues in libxl_devices.c .
The frontend path is
/local/domain/FRONTEND_DOMID/device/DEVICE_KIND/DEVID
The backend path is
/local/domain/BACKEND_DOMID/backend/BACKEND_KIND/FRONTEND_DOMID/DEVID
Often the BACKEND_DOMID is 0.
And looking into Linux kernel's xen-{blkfront,blkback} helps you a
lot.
Then you can switch xenbus state after proper values are in place, so
that frontend and backend can connect to each other.
Wei.
next prev parent reply other threads:[~2011-08-09 2:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-08 14:17 Block front and back connection Daniel Castro
2011-08-08 17:38 ` Pasi Kärkkäinen
2011-08-08 23:26 ` Reporting some xen 4.1.2* and 4.0 issues like limitations to 4 VCPUs for debian squeeze HVMs etc Mark Schneider
2011-08-09 0:55 ` Pasi Kärkkäinen
2011-08-09 21:05 ` Mark Schneider
2011-08-13 18:39 ` Pasi Kärkkäinen
2011-08-13 19:09 ` Reporting some xen 4.1.2* issues like limitations to 4 VCPUs for debian squeeze HVMs Mark Schneider
2011-08-23 17:57 ` Stefano Stabellini
2011-08-23 17:55 ` Pasi Kärkkäinen
2011-08-23 18:10 ` Stefano Stabellini
2011-08-23 18:45 ` Pasi Kärkkäinen
2011-08-23 18:54 ` Stefano Stabellini
2011-08-24 21:02 ` Konrad Rzeszutek Wilk
2011-08-25 20:09 ` Mark Schneider
2011-08-26 12:19 ` Stefano Stabellini
2011-08-09 2:27 ` Wei Liu [this message]
2011-08-09 8:38 ` Block front and back connection Daniel Castro
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=20110809022755.GA1783@limbo \
--to=liuw@liuw.name \
--cc=evil.dani@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).