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] Free XEN / DomU management software

To: Michael Schmidt <michael.schmidt@xxxxxxxxxx>
Subject: Re: [Xen-users] Free XEN / DomU management software
From: "Nuno L. Ferreira" <nunolf@xxxxxxxxx>
Date: Wed, 27 Jan 2010 22:18:44 +0100
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 27 Jan 2010 13:19:45 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=dXJX1+0BQDzeOm9N89rCZpeDazxUfqUTODgeiOsdAic=; b=hK/HvcZjHCR40EGMN3546P2NH6S9lGfOknfxVIqwa24WfdSwOr3L452bY9K/hncO9y ZUzkxWlktfx9YELSI8yPIyeGUF2pLErlVBQ36JVTHXz3DzdmTwftZfsXHvT5qDFRZFVK fl7jeyadIH8dMkbS1OZTI3nDCpicvQ9g9YN2U=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=Jd7TJohMLjUC4uA/ShPdKJ/BnHrcGZg6hVJkCjWS5wUtiI3ZyAytCcZ3WuCYqFteqy k8zIick9KPESDvfMrD8jAeDCqtaCZETl2MlIQbvRQBcJXuplLT9uDoDyD/wBakaZFZfB p4Q3/xHLcYtmuUPvmtSqEXrtM7SaV88SWcmoc=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4B60A991.90108@xxxxxxxxxx>
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAA85A/2Eg7pEKxWfiLe799XcKAAAAQAAAAml+PnoFJGk6AuDAdS2DnwAEAAAAA@xxxxxxxxxxxxxx> <4B60A5B0.10303@xxxxxxxxx> <4B60A991.90108@xxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/20100104 SeaMonkey/2.0.2
Hi Michael,

Here is the info you requested.
For the record, I installed the xn-suite on a dom0, which currently does not have any domU running. I thought it was possible already to use this dom0 as a centralized monitoring system ... have to wait 2 months more ;-)

[root@xxx ~]# uname -a
Linux xxx.yyy.zzz 2.6.18-128.7.1.el5xen #1 SMP Mon Aug 24 09:14:33 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux

[root@xxx ~]# head -1 /etc/issue
CentOS release 5.3 (Final)

[root@xxx ~]# xm info | grep xen_
xen_major              : 3
xen_minor              : 1
xen_extra              : .2-128.7.1.el5
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
xen_pagesize           : 4096
xen_changeset          : unavailable

[root@enmr00 ~]# ipcs -q

------ Message Queues --------
key        msqid      owner      perms      used-bytes   messages
0x22f9a7d1 0          root       666        0            0


Michael Schmidt wrote:

Hi *

Really great.
A few questions more.

1 - Can xn-suite monitor Xen domU's hosted in different dom0's? What is it done?

Currently - no. But we are currently working on a xmlrpc and a centraliced management interface.
I think it is (stable) done within <2 month.

2 - I did not saw it written anywhere, but I guess that the xn-client should be installed in every dom0 hosting domU's, right?

The xn-client provides the mem- and performance-data to his dom0.
If you want to use the modules xn-mem and xn-mom, you have to install the xn-client to each domU.

3 - I'm getting the following error:
*ERROR:* Can't comunicate with xn-manage-daemon! Check if the daemon is alive!
[root@xxx ~]# ps -ef | grep xn-
root 24286 1 0 21:10 pts/1 00:00:00 /usr/sbin/xn-manage-daemon -c /etc/xncore/xn-manage.conf root 24295 1 0 21:10 pts/1 00:00:00 /usr/sbin/xn-mem-daemon -c /etc/xncore/xn-mem.conf root 24305 1 0 21:10 pts/1 00:00:00 /usr/sbin/xn-mon-daemon -c /etc/xncore/xn-mon.conf root 24315 1 0 21:10 pts/1 00:00:00 /usr/sbin/xn-traff-daemon -c /etc/xncore/xn-traff.conf
root     24794 24155  0 21:35 pts/1    00:00:00 grep xn-

Looks like a problem with the IPC, can you run "ipcs -q" and send me the output? Or it is a bug with domU names who are longer then 32 chars or including a dot. If it is so, update to the version 0.82.

Tot ziens,

- Best Regards
Michael Schmidt

Xen-users mailing list