All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Guthro <bguthro@virtualiron.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: libxen domain creation
Date: Fri, 02 Nov 2007 08:59:13 -0400	[thread overview]
Message-ID: <472B1F21.4030404@virtualiron.com> (raw)

All,

I am making a first pass at using the C bindings of the Xen-API for a 
test application, and am running into some confusion on the proper use 
of the API.

I am modeling some of my development around the test code in 
tools/libxen/test/test_bindings.c
However, some things are not clear to me, and the API documentation 
seems to be more of a function reference, than documenting the intended 
usage of the functions I am interested in. Hopefully, this list can help 
in this regard.

During domain creation, an ultimate goal is to pair a physical drive, or 
file with the domain being created.
If we know our configuration going into domain creation (as we should) 
such that the backend is, say
/dev/sda1 and we want this to ultimately be visible as /dev/hda on the 
guest - how would I go about this?

I can see that the relationship in the API is such that
a host contains PBD's (Phys. Bock Devs)
PBD's contain SR's (Storage Repos)
SR's contain VDI's ((Virtual Disk Image)
and the VDI is what the VM ultimately sees as its disk.

Should I be looking up all PBD's from the host, and comparing it's name 
with my config value? What is the proper relationship between the 
"/dev/sda1" and PBDs?

Any and all help to clear up this confusion would be appreciated.

Ben

                 reply	other threads:[~2007-11-02 12:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=472B1F21.4030404@virtualiron.com \
    --to=bguthro@virtualiron.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.