From: Hollis Blanchard <hollisb@us.ibm.com>
To: xen-devel <xen-devel@lists.xensource.com>
Cc: Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>
Subject: [Fwd: [XenPPC] can't start xend - anyone similar problems or a hint for me ?]
Date: Tue, 08 May 2007 11:20:19 -0500 [thread overview]
Message-ID: <1178641219.30823.24.camel@basalt> (raw)
[-- Attachment #1: Type: text/plain, Size: 78 bytes --]
Is this a well-known error?
--
Hollis Blanchard
IBM Linux Technology Center
[-- Attachment #2: Forwarded message - [XenPPC] can't start xend - anyone similar problems or a hint for me ? --]
[-- Type: message/rfc822, Size: 10746 bytes --]
From: Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>
To: xen-ppc-devel@lists.xensource.com
Subject: [XenPPC] can't start xend - anyone similar problems or a hint for me ?
Date: Thu, 03 May 2007 16:47:53 +0200
Message-ID: <4639F619.8060403@linux.vnet.ibm.com>
Hi,
I can't start xend anymore and wanted to ask if anyone had similar
problems in the past.
Also every suggestion to solve that issue is very welcome - actually I
hope someone has a hint for me ;-)
It used to work before with some older source tree for xen & linux. I
tested my old xen/dom0 image that used to work together with the new
tools but that throws the same errors (I need to go to the new version
anyway so stepping back would be only a bug trackiong option anyway).
I already moved to the current head of xen-unstable.hg and
linux-ppc-2,6.hg and recompiled everything.
I used to build/boot debug images but the error occurs also with non
debug images.
Here I post the information what I got out of my logs on my system so
far. Important facts are:
- exception "metrics" ???
- there is some phyton/xen rocess listening on port 8002
xend.log:
INFO (SrvDaemon:331) Xend Daemon started
INFO (SrvDaemon:335) Xend changeset: Wed May 02 14:41:51 2007 +0100
14995:f3cf882c9578.
INFO (SrvDaemon:342) Xend version: Unknown.
WARNING (XendNode:147) Error recreating network
af23a262-339d-9043-66f3-56ae2d6d894a
ERROR (SrvDaemon:353) Exception starting xend ('metrics')
Traceback (most recent call last):
4430 File "//usr/lib/python/xen/xend/server/SrvDaemon.py", line
345, in run
4431 servers = SrvServer.create()
4432 File "//usr/lib/python/xen/xend/server/SrvServer.py", line
254, in create
4433 root.putChild('xend', SrvRoot())
4434 File "//usr/lib/python/xen/xend/server/SrvRoot.py", line 40,
in __init__
4435 self.get(name)
4436 File "//usr/lib/python/xen/web/SrvDir.py", line 82, in get
4437 val = val.getobj()
4438 File "//usr/lib/python/xen/web/SrvDir.py", line 52, in getobj
4439 self.obj = klassobj()
4440 File "//usr/lib/python/xen/xend/server/SrvNode.py", line 30,
in __init__
4441 self.xn = XendNode.instance()
4442 File "//usr/lib/python/xen/xend/XendNode.py", line 658, in
instance
4443 inst = XendNode()
4444 File "//usr/lib/python/xen/xend/XendNode.py", line 168, in
__init__
4445 XendPIF.recreate(pif, pif_uuid)
4446 File "//usr/lib/python/xen/xend/XendPIF.py", line 197, in recreate
4447 metrics_uuid = record['metrics']
4448 KeyError: 'metrics'
xend-debug.log:
1402 Xend started at Thu May 3 15:54:28 2007.
1403 Exception starting xend: 'metrics'
/var/log/messages:
c08b01-0 BLKTAPCTRL[3958]: blktapctrl: v1.0.0
c08b01-0 BLKTAPCTRL[3958]: Found driver: [raw image (aio)]
c08b01-0 BLKTAPCTRL[3958]: Found driver: [raw image (sync)]
c08b01-0 BLKTAPCTRL[3958]: Found driver: [vmware image (vmdk)]
c08b01-0 BLKTAPCTRL[3958]: Found driver: [ramdisk image (ram)]
c08b01-0 BLKTAPCTRL[3958]: Found driver: [qcow disk (qcow)]
c08b01-0 BLKTAPCTRL[3958]: Unable to start blktapctrl
netstat -eeapn | grep -E "(python|xen)"
tcp 0 0 0.0.0.0:8002 0.0.0.0:*
LISTEN 0 11050 2697/python
unix 2 [ ACC ] STREAM LISTENING 10848
2625/xenstored /var/run/xenstored/socket
unix 2 [ ACC ] STREAM LISTENING 10849
2625/xenstored /var/run/xenstored/socket_ro
unix 3 [ ] STREAM CONNECTED 10955
2625/xenstored /var/run/xenstored/socket
unix 3 [ ] STREAM CONNECTED 10951 2690/xenconsoled
ps axlf | grep xen
1 0 53 50 10 -5 0 0 xenwat S< ? 0:00 \_
[xenwatch]
1 0 54 50 10 -5 0 0 xb_rea S< ? 0:00 \_
[xenbus]
5 0 2625 1 18 0 2240 880 select S ? 0:00
xenstored --pid-file /var/run/xenstore.pid
1 0 2677 1 22 0 14780 5636 wait S ? 0:00
python /usr/sbin/xend start
5 0 2697 2677 18 0 31412 6912 futex Sl ? 0:00 \_
python /usr/sbin/xend start
5 0 2690 1 18 0 10384 556 select Sl ? 0:00
xenconsoled
0 0 4040 3943 15 0 3068 816 start S+ pts/0
0:00 \_ grep xen
--
Grüsse / regards,
Christian Ehrhardt
IBM Linux Technology Center, Open Virtualization
+49 7031/16-3385
Ehrhardt@linux.vmnet.ibm.com
Ehrhardt@de.ibm.com
IBM Deutschland Entwicklung GmbH
Vorsitzender des Aufsichtsrats: Johann Weihen
Geschäftsführung: Herbert Kircher
Sitz der Gesellschaft: Böblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294
_______________________________________________
Xen-ppc-devel mailing list
Xen-ppc-devel@lists.xensource.com
http://lists.xensource.com/xen-ppc-devel
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2007-05-08 16:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-08 16:20 Hollis Blanchard [this message]
2007-05-08 16:27 ` [Fwd: [XenPPC] can't start xend - anyone similar problems or a hint for me ?] Keir Fraser
2007-05-09 5:24 ` Christian Ehrhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1178641219.30823.24.camel@basalt \
--to=hollisb@us.ibm.com \
--cc=ehrhardt@linux.vnet.ibm.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.