[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: [Xen-users] xend not starting / Xen unstable 4.1 - pv_ops 2.6.32.15
Hello, I completely re-installed the distro hosting xen (centos 5.5) and now everything is working smoothly again ... -----Message d'origine----- De : yingbin wang [mailto:yingbin.wangyb@xxxxxxxxx] Envoyé : mercredi 23 juin 2010 21:14 À : Jean-Michel Favre Cc : xen-users@xxxxxxxxxxxxxxxxxxx Objet : Re: [Xen-users] xend not starting / Xen unstable 4.1 - pv_ops 2.6.32.15 I also met this problem : xend can not start. the error info in xend.log is the same. code: xen-unstable.hg 4.1 changelog : 21650 or 21608 pv-ops 2.6.32.15 commit : 01d9fbca207ec232c758d991d66466fc6e38349e, head : xen/stable-2.6.32.x I tested other combination(xen-unstable.hg 4.1 + pv-ops 2.6.31.13). The problem also appear. Have anybody started xend successfully in this combination(xen-unstable.hg 4.1 + pv-ops 2.6.32.15)? thanks! wyb 2010/6/16 Jean-Michel Favre <jean-michel.favre@xxxxxxxxxxx>: > Hello, > > I compiled xen-unstable 4.1 with Jeremy?s pv-ops 2.6.32.15. When I try to > start xend it aborts with the trace below in xend.log : > > > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++ > > [root@bart xen]# cat xend.log > > [2010-06-14 21:28:16 6631] INFO (SrvDaemon:332) Xend Daemon started > > [2010-06-14 21:28:16 6631] INFO (SrvDaemon:336) Xend changeset: Fri Jun 11 > 15:22:12 2010 +0100 21606:9f49e9794596. > > [2010-06-14 21:28:16 6631] DEBUG (tcp:96) Listening on :8002 > > [2010-06-14 21:28:18 6631] DEBUG (XendCPUPool:747) recreate_active_pools > > [2010-06-14 21:28:18 6631] ERROR (SrvDaemon:349) Exception starting xend > ((2, 'No such file or directory')) > > 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 258, 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 1176, > in instance > > inst = XendNode() > > File "usr/lib64/python2.4/site-packages/xen/xend/XendNode.py", line 163, > in __init__ > > self._init_cpu_pools() > > File "usr/lib64/python2.4/site-packages/xen/xend/XendNode.py", line 377, > in _init_cpu_pools > > XendCPUPool.recreate_active_pools() > > File "usr/lib64/python2.4/site-packages/xen/xend/XendCPUPool.py", line > 754, in recreate_active_pools > > uuid = xstransact.Read(path, 'uuid') > > File "usr/lib64/python2.4/site-packages/xen/xend/xenstore/xstransact.py", > line 307, in Read > > return complete(path, lambda t: t.read(*args)) > > File "usr/lib64/python2.4/site-packages/xen/xend/xenstore/xstransact.py", > line 361, in complete > > t = xstransact(path) > > File "usr/lib64/python2.4/site-packages/xen/xend/xenstore/xstransact.py", > line 29, in __init__ > > self.transaction = xshandle().transaction_start() > > File "usr/lib64/python2.4/site-packages/xen/xend/xenstore/xsutil.py", line > 18, in xshandle > > xs_handle = xen.lowlevel.xs.xs() > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++ > > > > Have somebody got any idea ? > > > > Thanks in advance > > Jean-Michel > > > > > > _______________________________________________ > Xen-users mailing list > Xen-users@xxxxxxxxxxxxxxxxxxx > http://lists.xensource.com/xen-users > _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |