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] bug report of xm list and xm vcpu-list

To: Yoshinori Katase <y_katase@xxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] bug report of xm list and xm vcpu-list
From: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Date: Thu, 22 Dec 2005 15:39:48 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 22 Dec 2005 15:42:54 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20051222093107.7C0561C006@xxxxxxxxxxxxxxxxxxxxxxxxx>
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: <20051222093107.7C0561C006@xxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Thu, Dec 22, 2005 at 06:31:39PM +0900, Yoshinori Katase wrote:

> Hi,
> 
> Xm list and xm vcpu-list show wrong DomID(name).
> Under this situation,
> # xm list
> Name                              ID Mem(MiB) VCPUs State  Time(s)
> Domain-0                           0      512     1 r-----  1064.6
> test1                             13       64     1 r----- 83879.7
> 
> # xm list 1 13
> Error: Domain '1' not found when running 'xm list'
> # xm list 13 15
> Error: Domain '13' not found when running 'xm list'
> 
> An error message shows always the first one of given DomIDs,
> when xm list is given unexistant DomIDs.
> This is serious, when many domains are running.

This is a problem with the exception reporting from Xend (the daemon) to xm
(the client tool).  The exception does not carry enough information to allow
xm to diagnose the problem correctly.  Please feel free to fix this (no-one
else is working on it at the moment).

Ewan.

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

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