From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: xend start error Date: Tue, 17 Feb 2009 15:06:02 -0800 Message-ID: <499B42DA.4060405@goop.org> References: <20090217123319.vxacc1ujxcc4woko@www.destar.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20090217123319.vxacc1ujxcc4woko@www.destar.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: jonr@destar.net Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org jonr@destar.net wrote: > Hello, > > uname -a > Linux null 2.6.29-rc5-tip-01984-g5812263 #1 SMP Tue Feb 17 07:28:09 > AKST 2009 i686 GNU/Linux > > I have followed Boris' guide at: > http://bderzhavets.wordpress.com/2009/02/17/setup-xen-unstable-dom0-via-2629-rc5-pv_ops-enabled-kernel-on-intel-sataahci/ > and after I reboot into the new rc5 kernel and try to start xend, I am > getting this error: > > 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 44, in > from xen.xend.server import SrvDaemon > File "//usr/lib/python/xen/xend/server/SrvDaemon.py", line 26, in > > import relocate > File "//usr/lib/python/xen/xend/server/relocate.py", line 28, in > > from xen.xend import XendDomain > File "//usr/lib/python/xen/xend/XendDomain.py", line 35, in > from xen.xend import XendOptions, XendCheckpoint, XendDomainInfo > File "//usr/lib/python/xen/xend/XendCheckpoint.py", line 20, in > > from xen.xend import balloon, sxp, image > File "//usr/lib/python/xen/xend/image.py", line 44, in > 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)') > > The only thing I think might be wrong is I did it in the wrong order. > Would installing the kernel first then Xen be an issue? It looks like you need to add xenfs /proc/xen xenfs defaults 0 0 to your /etc/fstab. J