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


[Xen-users] xm console stability

To: Xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] xm console stability
From: Jonathan Tripathy <jonnyt@xxxxxxxxxxx>
Date: Sat, 02 Oct 2010 12:29:35 +0100
Delivery-date: Sat, 02 Oct 2010 04:30:35 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20100713 Thunderbird/3.0.6
Hi Everyone,

Is anyone aware of any stability issues regarding xm console, especially when accessed by multiple users?

I created a setup where I ha a "front end" proxy server, which users ssh'ed into. This front end server then ssh'ed to the correct Xen node (using the same ssh key for all users). In the morning, the 2 servers that I was trailing the system out on were chocking to death (not sure why, as CPU was nearly idle...), and eventually when I tried to do something resource intensive (like image a new DomU using dd), the Dom0s just crashed and both servers needed a reboot. This happened on both of the servers...

Any ideas?

Using Xen 3.4.3 running on Centos 5.5 Dom0.


Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] xm console stability, Jonathan Tripathy <=