Xen devel - Jul 2010 - Xend start failing on fresh Xen installation

Hi,
>From the help I got on y last post, I was able to get Xen compiled and boot
the Dom0 successfully.
Now I am having trouble in getting xend to start.
It is failing with the following trace.
I have a fresh Xen install 4.0.1-rc5-pre with a x86_64 dom0.
I already commented out the relocation server line in
/etc/xen/xend-config.sxp

Any help or pointers will be much appreciated.

Thx,
Jon

[root@localhost jw]# xend start
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/xend", line 36, in <module>
    from xen.xend.server import SrvDaemon
  File
"/usr/lib64/python2.6/site-packages/xen/xend/server/SrvDaemon.py",
line 26, in <module>
    import relocate
  File
"/usr/lib64/python2.6/site-packages/xen/xend/server/relocate.py",
line 28, in <module>
    from xen.xend import XendDomain
  File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomain.py",
line 36,
in <module>
    from xen.xend import XendOptions, XendCheckpoint, XendDomainInfo
  File
"/usr/lib64/python2.6/site-packages/xen/xend/XendCheckpoint.py", line
20, in <module>
    from xen.xend import balloon, sxp, image
  File "/usr/lib64/python2.6/site-packages/xen/xend/image.py", line
46, 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)'')
[root@localhost jw]# uname -a
Linux localhost.localdomain 2.6.31.13 #1 SMP Wed Jul 21 23:55:51 PDT 2010
x86_64 x86_64 x86_64 GNU/Linux
[root@localhost jw]#


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

On 23/07/2010 09:42, "Jonathan White" <jonxwhite@gmail.com>
wrote:
>   File "/usr/lib64/python2.6/site-packages/xen/xend/image.py",
line 46, 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)'')
> [root@localhost jw]# uname -a
> Linux localhost.localdomain 2.6.31.13 #1 SMP Wed Jul 21 23:55:51 PDT 2010
> x86_64 x86_64 x86_64 GNU/Linux
> [root@localhost jw]#
You might need this line in /etc/fstab:
none /proc/xen xenfs defaults 0 0

 -- Keir



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

Thanks a lot. That worked. Now xm list shows the dom0. :)

On Fri, Jul 23, 2010 at 1:53 AM, Keir Fraser
<keir.fraser@eu.citrix.com>wrote:
> On 23/07/2010 09:42, "Jonathan White" <jonxwhite@gmail.com>
wrote:
>
> >   File
"/usr/lib64/python2.6/site-packages/xen/xend/image.py", line 46,
> 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)'')
> > [root@localhost jw]# uname -a
> > Linux localhost.localdomain 2.6.31.13 #1 SMP Wed Jul 21 23:55:51 PDT
2010
> > x86_64 x86_64 x86_64 GNU/Linux
> > [root@localhost jw]#
>
> You might need this line in /etc/fstab:
> none /proc/xen xenfs defaults 0 0
>
>  -- Keir
>
>
>

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

On Fri, 2010-07-23 at 09:53 +0100, Keir Fraser wrote:
> On 23/07/2010 09:42, "Jonathan White" <jonxwhite@gmail.com>
wrote:
> 
> >   File
"/usr/lib64/python2.6/site-packages/xen/xend/image.py", line 46, 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)'')
> > [root@localhost jw]# uname -a
> > Linux localhost.localdomain 2.6.31.13 #1 SMP Wed Jul 21 23:55:51 PDT
2010
> > x86_64 x86_64 x86_64 GNU/Linux
> > [root@localhost jw]#
> 
> You might need this line in /etc/fstab:
> none /proc/xen xenfs defaults 0 0
tools/hotplug/Linux/init.d/xend (which becomes /etc/init.d/xend on
install) takes care of this automatically, looks like this behaviour was
in 4.0.1-rc5. Using the initscript rather than manually starting the
daemon is probably to be advised, even if you only run the initscript
manually.

Ian.


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