From: Keir Fraser <keir.fraser@eu.citrix.com>
To: AP Xen <apxeng@gmail.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
"'Vincent, Pradeep'" <pradeepv@amazon.com>
Cc: Ian,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Jackson <Ian.Jackson@eu.citrix.com>,
'Dulloor' <dulloor@gmail.com>
Subject: Re: New feature support - xl or xm ?
Date: Thu, 10 Jun 2010 21:19:02 +0100 [thread overview]
Message-ID: <C8370746.2A61%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <001201cb08d7$d2caad80$78600880$@com>
On 10/06/2010 21:02, "AP Xen" <apxeng@gmail.com> wrote:
>> We like the 'xm' CLI, in fact we are trying our best to provide a
>> compatible command line interface with 'xl'.
>> Ideally you'll be able to symlink xl to xm and everything will still
>> work. If you find any problem with command line incompatibilities
>> please let us know, and we'll fix them.
>>
>> On the other hand if you are speaking about the XML-RPC interface
>> provided by xend, that is a totally different matter.
>
> So with xl, xend doesn't need to be running as it uses the libxl API which
> bypasses libxenguest/xend?
All correct, except libxl does use libxenctrl and libxenguest. But it does
not use xend and so does not need it to be running.
-- Keir
next prev parent reply other threads:[~2010-06-10 20:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-28 22:37 New feature support - xl or xm ? Dulloor
2010-05-28 22:41 ` Stefano Stabellini
2010-06-01 10:20 ` Ian Jackson
2010-06-08 1:35 ` Vincent, Pradeep
2010-06-08 9:17 ` Stefano Stabellini
2010-06-08 22:49 ` Vincent, Pradeep
2010-06-08 23:37 ` Vincent, Pradeep
2010-06-09 15:09 ` Stefano Stabellini
2010-06-09 17:30 ` Vincent, Pradeep
2010-06-10 20:02 ` AP Xen
2010-06-10 20:19 ` Keir Fraser [this message]
2010-06-09 14:43 ` Stefano Stabellini
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=C8370746.2A61%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=apxeng@gmail.com \
--cc=dulloor@gmail.com \
--cc=pradeepv@amazon.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).