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] [PATCH] Improve xm error if booted native

To: Jim Fehlig <jfehlig@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Improve xm error if booted native
From: Zhigang Wang <zhigang.x.wang@xxxxxxxxxx>
Date: Wed, 04 Feb 2009 09:50:37 +0800
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, dexuan.cui@xxxxxxxxx
Delivery-date: Tue, 03 Feb 2009 17:51:40 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4988C692.5000506@xxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4988C692.5000506@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.19 (X11/20081209)
hi jim/dexuan,

I think using xen.lowlevel.xc here is totally wrong.

xm is client that designed to run on any host.

we should first try to replace the xc with other other functions. or add
a XenAPI/legacyAPI to use by xm.

thanks,

zhigang

Jim Fehlig wrote:
> Another trivial "user experience" patch that's been requested one too
> many times ...
> 
> -----------------------------------------
> 
> How to reproduce:
> i) boot default kernel (i.e. not xen kernel)
> ii) run xm list
> 
> Actual Result:
> calculon:/tmp # uname -a
> Linux calculon.suse.cz 2.6.27.11-1-default #1 SMP 2009-01-14 23:28:13 +0100
> x86_64 x86_64 x86_64 GNU/Linux
> calculon:/tmp # xm list
> ERROR Internal error: Could not obtain handle on privileged command interface
> (2 = No such file or directory)
> Traceback (most recent call last):
>   File "/usr/sbin/xm", line 8, in <module>
>     from xen.xm import main
>   File "/usr/lib64/python2.6/site-packages/xen/xm/main.py", line 61, in
> <module>
>     xc = xen.lowlevel.xc.xc()
> xen.lowlevel.xc.Error: (1, 'Internal error', 'Could not obtain handle on
> privileged command interface (2 = No such file or directory)')
> calculon:/tmp #   
> 
> Expected result:
> A more descriptive error message and no python traceback.
> 
> -----------------------------------------
> 
> Looking at the various xc_interface_open() impls in
> tools/libxc/xc_{linux,minios,netbsd,solaris}.c, it seems the most likely
> reason to fail is not booted xen.  I added a comment in the error
> suggesting this to user, e.g.
> 
> xen67:~ # xm li
> ERROR Internal error: Could not obtain handle on privileged command
> interface (2 = No such file or directory)
> Is xen kernel running?
> 
> The suggestion can go if you like but IMO we should suppress the
> traceback :-).
> 
>      Signed-off-by: Jim Fehlig <jfehlig@xxxxxxxxxx>
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel


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

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