From: Ian Campbell <ian.campbell@citrix.com>
To: kumara rathnavel <kumara.bsd@gmail.com>, xen-devel@lists.xen.org
Subject: Re: libxen-light
Date: Mon, 21 Sep 2015 09:27:13 +0100 [thread overview]
Message-ID: <1442824033.10338.1.camel@citrix.com> (raw)
In-Reply-To: <CA+NzLaMuyk8MpuCf7wAfT+43gPs4gx7BUn+ksE63o8zeoT6VrQ@mail.gmail.com>
On Mon, 2015-09-21 at 11:56 +0530, kumara rathnavel wrote:
> Hello,
>
> I do not find any proper documentation regarding API provided by the
> Libxenlight. All I find is the documentation for the xl that in turn uses
> Libxl Library. But I would like to use the library calls directly, I am
> able to basic operations like listing vm, reboot and all those . But when
> it comes to creation of domain or attaching device , I am filling the
> structures the same way as xl is doing. But I get a Seg Fault. Can you
> share some documentation on the Libxenlight API if possible or guidance
> would do,,.....
The documentation is mainly in the headers, starting with libxl.h.
If you have specific questions then please provide the code as well as the
error (e.g. the stack trace).
Ian.
prev parent reply other threads:[~2015-09-21 8:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 6:26 libxen-light kumara rathnavel
2015-09-21 8:27 ` Ian Campbell [this message]
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=1442824033.10338.1.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=kumara.bsd@gmail.com \
--cc=xen-devel@lists.xen.org \
/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).