From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jerry Gulla <jgulla@gmail.com>
Subject: Status of "management port" in 3.0?
Date: Fri, 23 Sep 2005 13:43:07 -0400
Message-ID: <ca21afba0509231043dce0168@mail.gmail.com>
Reply-To: Jerry Gulla <jgulla@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

I (finally) got Apache->mod_python->xend working so I can use the
(currently somewhat limited) web UI for Xen 3.0.  In Xen 2.0, there
was a process listening on  port 8000 that allowed an application to
query / change the configuration; I believe this is how gXenophilia
worked.

It seems as if in 3.0, however, nobody is listening on this port any
more. I've modified /etc/xen/xend-config.sxp to specify a port (and
open up more than 'localhost'), but this doesn't seem to have an
effect.

Is this going to be working some time in the near future for Xen 3.0,
or am I missing something (again :-)?

Thanks,

Jerry