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-users] discovering Xen version

To: Andrew Thompson <andrewkt@xxxxxxxxxxx>
Subject: Re: [Xen-users] discovering Xen version
From: aq <aquynh@xxxxxxxxx>
Date: Sat, 4 Jun 2005 15:29:00 +0900
Cc: ian.pratt@xxxxxxxxxxxx, Xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sat, 04 Jun 2005 06:28:14 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=sUBl5oLW8GmACRRk48lopWPVeBbwTj0iTVI5AJcokICaQai/w6tapuS4MlhvFRGcXnvMGLbfKJt9wstURVyt0o8gVr+0vBlJipftF95yvJGAXbrFQTcDJGtUvv/tuQjDCVJN8NR4V4Fe5uv1KiACDi6x0+FtSgVCvTh7jTBa91w=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <42A11536.7060301@xxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <A95E2296287EAD4EB592B5DEEFCE0E9D282061@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <42A11536.7060301@xxxxxxxxxxx>
Reply-to: aq <aquynh@xxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On 6/4/05, Andrew Thompson <andrewkt@xxxxxxxxxxx> wrote:
> Ian Pratt wrote:
> >>Is there a command which returns the version of Xen runing
> >>(i.e. 2.0.5, 3.0-devel), similar to the uname(1) command?  At
> >>first I thought "xm info" would provide it, but that doesn't
> >>appear to be the case.  Using "xm dmesg" one can see the
> >>version banner from Xen's message buffer, but isn't possible
> >>the message buffer could wrap or be cleared?
> >
> > It's on the 'todo' list to add to 'xm info'. Patches welcome :-)

Ian, is this what you named "xm --version" in todo list? if not, what
it is? (so vague!
> I'm 100% new to python, but I've figured out where to add code to make
> this show up in xm info. (Already tested with dummy data.)
> Can anyone tell me what object or function I could squeeze to get the
> Xen version number?

it is not that trivial. you must hack up here and there... for
example, it is necessary to extend python wrapper for this.

> Also, what should the label be called? I started with "xenversion", but
> wasn't sure if it should be xen or xend.

no, xen and xend are different things: xen is hypervisor, and xend is daemon.

btw, i am hacking this, and almost done. will post a patch soon.


Xen-users mailing list