WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] xm commands run very slow ....

To: Himanshu Raj <rhim@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] xm commands run very slow ....
From: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Date: Wed, 25 Jan 2006 10:05:43 -0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 25 Jan 2006 18:14:33 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20060125141912.GB8956@xxxxxxxxxxxxx>
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: <20060125141912.GB8956@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Wed, Jan 25, 2006 at 09:19:12AM -0500, Himanshu Raj wrote:

> Hi Folks,
> 
> I know it is kind of vague problem, but I am banking of somebody seeing the 
> exact thing.
> 
> I have two machines with everything identical, except on one machine I compile
> xen and on other I just use the binaries compiled on the previous machine.
> 
> Now on first machine, where I compile everything, xm invocation is 
> veeeeeeeeeery
> slow. Although it doesn't seem to be "system" problem. Look at a 
>         time xm list 
> invocation:
>         real 32s
>         user .2s
>         sys  .02s
> 
> On another machine the real time is very close to user+sys.
> 
> I just can't comprehend why this is going on. Any clues will be deeply 
> appreciated.

xm is a client to Xend, talking over HTTP -- xm is simply blocking for 30
seconds waiting for the server -- you need to figure out why the server is
spinning or stalling.

/var/log/xend.log may help.  top may help also.

Ewan.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>