On Mon, Jun 07, 2010 at 03:25:48PM +0200, Michal Novotny wrote:
>>>>>>>
>>>>>> Do you have xen-evtchn driver loaded?
>>>>>>
>>>>>>
>>>>>> -- Pasi
>>>>>>
>>>>> Well, no, and doesn't seem to be installed/probed:
>>>>>
>>>>> # modprobe xen-evtchn
>>>>> # lsmod | grep xen-evtchn
>>>>> #
>>>>>
>>>>> So there's the problem :(
>>>>>
>>>>> Michal
>>>> Oh, I'm taking this back since I found out the module is not xen-evtchn
>>>> but xen_evtchn. So yeah, I'm having it loaded in the memory now.
>>>> However, when I do `service xend restart` the same error is here:
>>>>
>>>> [2010-06-07 17:14:09 5635] INFO (SrvDaemon:227) Xend stopped due to
>>>> signal 15.
>>>> [2010-06-07 17:14:09 6295] INFO (SrvDaemon:332) Xend Daemon started
>>>> [2010-06-07 17:14:09 6295] INFO (SrvDaemon:336) Xend changeset: Thu May
>>>> 20 17:22:15 2010 +0100 21442:a7fcf2e35d32.
>>>> [2010-06-07 17:14:09 6295] DEBUG (tcp:96) Listening on :8002
>>>> [2010-06-07 17:14:09 6295] INFO (XendNetwork:114) Not recreating
>>>> missing
>>>> unmanaged network eth0
>>>> [2010-06-07 17:14:09 6295] INFO (XendNetwork:114) Not recreating
>>>> missing
>>>> unmanaged network eth2
>>>> [2010-06-07 17:14:09 6295] INFO (XendNetwork:114) Not recreating
>>>> missing
>>>> unmanaged network br0
>>>> [2010-06-07 17:14:09 6295] INFO (XendNetwork:114) Not recreating
>>>> missing
>>>> unmanaged network xenbr0
>>>> [2010-06-07 17:14:10 6295] DEBUG (XendCPUPool:747)
>>>> recreate_active_pools
>>>> [2010-06-07 17:14:10 6295] ERROR (SrvDaemon:349) Exception starting
>>>> xend
>>>> ((111, 'Connection refused'))
>>>> 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()
>>>> Error: (111, 'Connection refused')
>>>>
>>>> Any ideas?
>>>>
>>> Is xenstore running?
>>>
>>> Are there files in /proc/xen ?
>>>
>>
>> Yes to both questions. Everything seems to be OK. Also, there's option
>> to turn on the debugging of xenstore, right? Do you think it could
>> help? I'm going to try it now.
>>
>> Michal
>
> Well, I don't know what was wrong but when I turned on the debugging it
> was finally working fine to run xen daemon and also when I killed
> xenstore and turned off the debugging. `xm list` was working fine but I
> don't know why so it's a kind of magic to me. Nevertheless, it appears
> to be working fine by now.
>
Ok, good to hear it works now :)
-- Pasi
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home