This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Error getting VM-informations with Python on Xen 3.0.2

To: Thorolf Godawa <nospam@xxxxxxxxx>
Subject: Re: [Xen-devel] Error getting VM-informations with Python on Xen 3.0.2
From: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Date: Thu, 6 Apr 2006 14:06:36 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 06 Apr 2006 06:06:55 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20060406130523.GA18691@xxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4434197A.8000308@xxxxxxxxx> <20060406002723.GB30672@xxxxxxxxxxxxxxxxxxxxxx> <4434D940.9050004@xxxxxxxxx> <20060406130523.GA18691@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Thu, Apr 06, 2006 at 02:05:23PM +0100, Ewan Mellor wrote:

> On Thu, Apr 06, 2006 at 11:02:56AM +0200, Thorolf Godawa wrote:
> > Hi Ewan,
> > 
> > >Try server.xend.domains(True).  This changed with the new XML-RPC
> > >interface, courtesy of the aforementioned hacker.
> > thanks a lot, this solved my problem :-)))
> > 
> > Is there any documentation how to use these Python-interfaces?
> No, I'm afraid not.  The XML-RPC interface will stabilise in time, but at the
> moment, it's not documented.  The Python interface on top of the XML-RPC is
> not documented either, since it's only a stub onto the XML-RPC, now.
> The only interfaces that are guaranteed currently are those required to
> support old guests on new hypervisors.  Everything else is subject to change.
> The best way for you to keep up is to get your code into the tree, preferably
> with a unit test or two, and then there's a fair chance that it won't be
> broken as things change.

And improvements to the documentation are always welcome: if you want to write
up a tutorial, it would be gratefully received.


Xen-devel mailing list