[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] xen won't start


  • To: matt@xxxxxxxxxxxxxxxxxx
  • From: Alaa eldin <sirash23@xxxxxxxxx>
  • Date: Tue, 2 Mar 2010 05:22:09 -0500
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 02 Mar 2010 02:23:02 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=cxHr0AISuFufGDmmcpomoJp6UETcON/N6UfDE2Vhjt360ALTprylAew8Cn52KGtpgv 5nRBqI9OVvWQvHlNctV9y/BSq9kXrnlZia6jfcFsze3jiRYxOUS+g1BOjXCrVXVgPU6z vIwRiEH+9JY9Qxi5s7GukrsJFsBiQDQ1h7/DM=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

default=1
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title CentOS (2.6.18-164.el5xen)
    root (hd0,0)
    kernel /xen.gz-3.4.2
module /vmlinuz-2.6.18-164.el5xen ro root=/dev/VolGroup00/Lvroot
module /initrd-2.6.18-164.el5xen.img
title CentOS (2.6.18-164.11.1.el5xen)
    root (hd0,0)
    kernel /xen.gz-3.4.2
module /vmlinuz-2.6.18-164.11.1.el5xen ro root=/dev/VolGroup00/Lvroot
module /initrd-2.6.18-164.11.1.el5xen.img


On Tue, Mar 2, 2010 at 5:17 AM, Matthew Law <matt@xxxxxxxxxxxxxxxxxx> wrote:

You often see this error after doing a 'yum update' or equivalent.  Check
that the reference to the xen bits in your grub config is pointing to the
correct version and number you expect.

HTH,

Matt.

On Tue, March 2, 2010 10:11 am, Ian Tobin wrote:
> How have you built your OS? Is this the first build?
>
>
>
> Ian
>
>
>
>
>
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Alaa eldin
> Sent: 02 March 2010 10:03
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-users] xen won't start
>
>
>
> Hello,
> when i try to start the xen and write
> xm list
> the result
> Error: Unable to connect to xend: No such file or directory. Is xend
> running?
> and this
> /var/log/xen/xend.log
> [2010-03-02 05:00:00 3485] INFO (SrvDaemon:227) Xend stopped due to
> signal 15.
> [2010-03-02 05:00:00 3743] INFO (SrvDaemon:332) Xend Daemon started
> [2010-03-02 05:00:00 3743] INFO (SrvDaemon:336) Xend changeset:
> unavailable.
> [2010-03-02 05:00:00 3743] ERROR (SrvDaemon:349) Exception starting xend
> ((13, 'Permission denied'))
> Traceback (most recent call last):
>   File
> "/usr/lib64/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line
> 341, in run
>     servers = SrvServer.create()
>   File
> "/usr/lib64/python2.4/site-packages/xen/xend/server/SrvServer.py", line
> 251, in create
>     root.putChild('xend', SrvRoot())
>   File "/usr/lib64/python2.4/site-packages/xen/xend/server/SrvRoot.py",
> line 40, in __init__
>     self.get(name)
>   File "/usr/lib64/python2.4/site-packages/xen/web/SrvDir.py", line 84,
> in get
>     val = val.getobj()
>   File "/usr/lib64/python2.4/site-packages/xen/web/SrvDir.py", line 52,
> in getobj
>     self.obj = klassobj()
>   File "/usr/lib64/python2.4/site-packages/xen/xend/server/SrvNode.py",
> line 30, in __init__
>     self.xn = XendNode.instance()
>   File "/usr/lib64/python2.4/site-packages/xen/xend/XendNode.py", line
> 948, in instance
>     inst = XendNode()
>   File "/usr/lib64/python2.4/site-packages/xen/xend/XendNode.py","Ian
Tobin" <itobin@xxxxxxxxxxxxx> line
> 91, in __init__
>     self.other_config["xen_pagesize"] =
> self.xeninfo_dict()["xen_pagesize"]
>   File "/usr/lib64/python2.4/site-packages/xen/xend/XendNode.py", line
> 937, in xeninfo_dict
>     return dict(self.xeninfo())
>   File "/usr/lib64/python2.4/site-packages/xen/xend/XendNode.py", line
> 881, in xeninfo
>     info['xen_scheduler'] = self.xenschedinfo()
>   File "/usr/lib64/python2.4/site-packages/xen/xend/XendNode.py", line
> 871, in xenschedinfo
>     sched_id = self.xc.sched_id_get()
> Error: (13, 'Permission denied')
>
> OS : centos 5.4
> xen version : 3.4.2


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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.